VMware Cloud Community
Bri1
Contributor
Contributor

HQ Server fails to start

I'm running 3.0.2 server on a Gentoo box. Everything was going fine for the last week or so, but then...


Starting HQ server...
Initializing HQ server configuration...
Checking jboss jndi port...
Checking jboss mbean port...
Starting HQ built-in database...
HQ built-in database failed to start:
The log file /hyperic/server-3.0.2/hqdb/data/hqdb.log may contain further details on why it failed to start.


[2007-04-16 12:48:37.421 CDT] LOG: could not bind IPv4 socket: Address already in use
[2007-04-16 12:48:37.421 CDT] HINT: Is another postmaster already running on port 9432? If not, wait a few seconds and retry.
[2007-04-16 12:48:37.422 CDT] FATAL: could not create shared memory segment: Invalid argument
[2007-04-16 12:48:37.422 CDT] DETAIL: Failed system call was shmget(key=9432001, size=85368832, 03600).
[2007-04-16 12:48:37.422 CDT] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 85368832 bytes), reduce PostgreSQL's shared_buffers parameter (currently 10000) and/or its max_connections parameter (currently 100).
If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared memory configuration.


There are no other devices with this IP and nothing runs on that port.
0 Kudos
2 Replies
excowboy
Virtuoso
Virtuoso

During install HQ tunes your Kernel parameter. Maybe there was a kernel upgrade or your kernel specific configuration has changed...
If you still have your hyperic-install directory run the following script again:

/hyperic-hq-installer/installer-3.0.2/data/hqdb/tune-os.sh

or add to your /etc/sysctl.conf the following line

kernel.shmmax=2147483648
0 Kudos
Bri1
Contributor
Contributor

Thanks for the info, that script fixed things up.

I didn't realize that the initial install script made that change, so I was hesitant to poke around.
0 Kudos