[OpenSER-Users] 1.3.2 Startup Problem

[Michael Young]

Sorry, I reposted that message under the same subject as before, so I didn't think I was hijacking anything. I didn't get any responses when I posted this a few weeks ago.

My problem appears to be a physical problem... I ordered 4 Gb of RAM in this server, and it seems it only has 2 Gb installed. When I back the -m option down to 2048 it works.

Michael


-----Original Message-----
From: Henning Westerholt [mailto:henning.westerholt at 1und1.de] 
Sent: Monday, July 07, 2008 10:13 AM
To: users at lists.openser.org
Cc: Michael Young
Subject: Re: [OpenSER-Users] 1.3.2 Startup Problem

On Monday 07 July 2008, Michael Young wrote:
> I just yum updated a CentOS box to 5.2 (kernel 2.6.18-92.1.1, i386), and
> now openserctl start no longer works. When I try it, I get this in the
> messages file:
>
> Jun 27 08:44:49 proxy1 openser: CRITICAL:core:shm_getmem: could not attach
> shared memory segment: Invalid argument
>
> Jun 27 08:44:49 proxy1 openser: CRITICAL:core:init_shm_mallocs: could not
> initialize shared memory pool, exiting...
>
> I can start openser with /usr/local/sbin/openser, and it starts fine. The
> openserctlrc file is the same as it is on each server I have, it works
> everywhere else. I try turning up logging, turning on debug, and I get
> nothing but those two lines in the log.
>
> Any ideas? Where do I start to troubleshoot this?

Hi Michael,

please don't hijack an existing mail thread for your questions, use a new one 
instead.

This error message could indicate that the server requested to much memory if 
started from this script. Perhaps the new kernel setup a smaller limit for 
the SHMMAX parameter? The reason that it works with the init script could be 
that this starts the server with fewer shared memory. Try to decrease the 
shared memory pool setting for openser.

Cheers,

Henning
No virus found in this incoming message.
Checked by AVG - http://www.avg.com 
Version: 8.0.136 / Virus Database: 270.4.6/1538 - Release Date: 7/7/2008 7:40 AM