Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id D0084B5F79E for ; Tue, 31 May 2011 14:47:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 79689-10 for ; Tue, 31 May 2011 17:47:52 +0000 (UTC) X-Greylist: delayed 00:05:08.858523 by SQLgrey-1.7.6 Received: from SVRMAILCAS1.padres.com (unknown [209.242.156.253]) by mail.postgresql.org (Postfix) with ESMTP id 76839B5F721 for ; Tue, 31 May 2011 14:47:52 -0300 (ADT) Received: from SVRMAIL2.padres.com ([fe80::cd8c:f07:aff2:301c]) by SVRMAILCAS1.padres.com ([fe80::d9c2:9ee3:f744:47a%10]) with mapi id 14.01.0289.001; Tue, 31 May 2011 10:40:28 -0700 From: Wells Oliver To: "pgsql-admin@postgresql.org" Subject: Server crash... trying to figure it out Thread-Topic: Server crash... trying to figure it out Thread-Index: AQHMH7nUln5n2rVvhUaavmicBoBi/w== Date: Tue, 31 May 2011 17:40:28 +0000 Message-ID: <509F1BCA-2A75-41F4-87F5-EBD098023D71@padres.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.31.12.124] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.107 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RDNS_NONE=0.793 X-Spam-Level: X-Archive-Number: 201105/185 X-Sequence-Number: 37622 This has happened twice over the last couple of nights: 2011-05-30 02:08:27 PDT LOG: server process (PID 29979) was terminated by = signal 9: Killed 2011-05-30 02:08:27 PDT LOG: terminating any other active server processes 2011-05-30 02:08:31 PDT LOG: all server processes terminated; reinitializi= ng 2011-05-30 02:08:31 PDT FATAL: could not create shared memory segment: Can= not allocate memory 2011-05-30 02:08:31 PDT DETAIL: Failed system call was shmget(key=3D543200= 1, size=3D6595420160, 03600). 2011-05-30 02:08:31 PDT HINT: This error usually means that PostgreSQL's r= equest for a shared memory segment exceeded available memory or swap space.= To reduce the request size (currently 6595420160 bytes), reduce PostgreSQL= 's shared_buffers parameter (currently 786432) and/or its max_connections p= arameter (currently 203). The PostgreSQL documentation contains more information about shared memory= configuration. There isn't much server load at the time: the only messages in the log are = the annoying autovacuum finding orphan temp tables b/c people haven't close= d out their sessions. I'm guessing it's unrelated, but I'm not entirely sur= e. The value of shared_buffers is set to 6GB, work_mem is 64MB, maintenance_wo= rk_mem is 128MB, effective_cache_size is 4GB. max_connections is set to 200. Any ideas here? The system has 12GB; raising the shared_buffers seems reaso= nable but 6GB also feels like it should be sufficient. Any thoughts appreciated. Thanks! -- Wells Oliver Architect, Baseball Systems 619-795-5359 San Diego Padres | 100 Park Boulevard | San Diego CA 92101