From jedi at jedimercer.com Wed Jun 15 14:09:44 2011 From: jedi at jedimercer.com (Jedi Mercer) Date: Wed, 15 Jun 2011 17:09:44 -0400 (EDT) Subject: [nexpose-users] Borked update Message-ID: I started up Nexpose on my home box and let it update, but it borked something and is now in Maint mode. The log says this: NSC 2011-06-15T21:04:55 Database initialization failed : java.sql.SQLException: Error starting PostgreSQL: com.rapid7.os.OSException: Could not start the nxpgsql daemon at com.rapid7.nexpose.datastore.A.K.E(Unknown Source) at com.rapid7.nexpose.datastore.n.H(Unknown Source) at com.rapid7.nexpose.datastore.n.E(Unknown Source) at com.rapid7.nexpose.datastore.n.E(Unknown Source) at com.rapid7.nexpose.nsc.NSC.U(Unknown Source) at com.rapid7.nexpose.nsc.NSC.?(Unknown Source) at com.rapid7.nexpose.nsc.NSC.?(Unknown Source) at com.rapid7.nexpose.nsc.NSC.run(Unknown Source) at com.rapid7.nexpose.nsc.NSC.main(Unknown Source) Caused by: com.rapid7.os.OSException: Could not start the nxpgsql daemon at com.rapid7.nexpose.datastore.A.K.A(Unknown Source) ... 9 more SQLState=null, errorCode=0 Annoyingly, I can't login to maintenance mode,keeps giving me a login failure, >:( From jedi at jedimercer.com Wed Jun 15 17:31:10 2011 From: jedi at jedimercer.com (Jedi Mercer) Date: Wed, 15 Jun 2011 20:31:10 -0400 (EDT) Subject: [nexpose-users] Borked update In-Reply-To: <4DF9256A.9030805@metasploit.com> References: <4DF9256A.9030805@metasploit.com> Message-ID: [frogging] So it looks like Postgres is demanding more memory than SHMMAX is configured for: FATAL: could not create shared memory segment: Invalid argument DETAIL: Failed system call was shmget(key=5432001, size=37978112, 03600). 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 37978112 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 104). 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. I'm not sure how it got to think I have 32GB when I only have 8GB, :) From Prashanth_Ram at rapid7.com Wed Jun 15 19:38:27 2011 From: Prashanth_Ram at rapid7.com (Prashanth Ram) Date: Thu, 16 Jun 2011 02:38:27 +0000 Subject: [nexpose-users] Borked update In-Reply-To: References: <4DF9256A.9030805@metasploit.com> Message-ID: <78A8F382002A28438F55C2E5352DF19502680F@BOSTONEX.tor.rapid7.com> Hmmm - looks like a known Ubuntu 9.10 + pgsql 8.4: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/264336 Some have found sols. for this issue.. " #39 - I had the same issue with Debian squeeze and PostgreSQL today. The solution was to add a line: kernel.shmmax = 41943040 to file /etc/sysctl.conf . Maybe it will help yo." Prashanth -----Original Message----- From: nexpose-users-bounces at lists.rapid7.com [mailto:nexpose-users-bounces at lists.rapid7.com] On Behalf Of Jedi Mercer Sent: Wednesday, June 15, 2011 8:31 PM To: nexpose-users at lists.rapid7.com Subject: Re: [nexpose-users] Borked update [frogging] So it looks like Postgres is demanding more memory than SHMMAX is configured for: FATAL: could not create shared memory segment: Invalid argument DETAIL: Failed system call was shmget(key=5432001, size=37978112, 03600). 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 37978112 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 104). 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. I'm not sure how it got to think I have 32GB when I only have 8GB, :) _______________________________________________ http://community.rapid7.com/redmine/projects/nexpose/wiki https://mail.metasploit.com/mailman/listinfo/nexpose-users