X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6DDFA54D70 for ; Fri, 4 Mar 2005 17:50:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 36915-01 for ; Fri, 4 Mar 2005 17:50:36 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 094FB54D05 for ; Fri, 4 Mar 2005 17:50:35 +0000 (GMT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 04 Mar 2005 11:50:34 -0600 Subject: Re: PG shutdown itself? From: Scott Marlowe To: Lee Wu Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-Id: <1109958634.30529.426.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 04 Mar 2005 11:50:34 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/48 X-Sequence-Number: 16546 On Fri, 2005-03-04 at 11:38, Lee Wu wrote: > Greetings, >=20 > =20 >=20 > To best of my knowledge, nobody issued pg_ctl stop =E2=80=93m fast while=20 >=20 > we experienced PG was trying to shutdown unsuccessfully: >=20 > =20 >=20 > *** Everything seems normal before this point *** >=20 > Mar 3 21:07:55 myhost postgres[630]: [24] LOG: recycled transaction > log file 00001ABC0000006D >=20 > Mar 3 21:08:57 myhost postgres[5158]: [1] LOG: fast shutdown request >=20 > Mar 3 21:08:57 myhost postgres[5158]: [2] LOG: aborting any active > transactions >=20 > Mar 3 21:08:57 myhost postgres[14292]: [1] FATAL: This connection > has been terminated by the administrator. >=20 > *** A lot of =E2=80=9CThis connection has been terminated by the > administrator.=E2=80=9D taken out here *** >=20 > Mar 3 21:08:57 myhost postgres[15912]: [3] FATAL: The database > system is shutting down >=20 > *** A lot the same message as last line till *** >=20 > Mar 3 22:10:39 myhost postgres[1840]: [3] FATAL: The database system > is shutting down >=20 > =20 >=20 > Then I used =E2=80=9C=E2=80=93m immediate=E2=80=9D: >=20 > Mar 3 22:10:39 myhost postgres[5158]: [3] LOG: immediate shutdown > request >=20 > Mar 3 22:11:07 myhost postgres[1918]: [1] LOG: database system was > interrupted at 2005-03-03 21:08:53 MST >=20 > Mar 3 22:11:07 myhost postgres[1918]: [2] LOG: checkpoint record is > at 1ABC/929DFCB4 >=20 > Mar 3 22:11:07 myhost postgres[1918]: [3] LOG: redo record is at > 1ABC/9044F3B4; undo record is at 0/0; shutdown FALSE >=20 > Mar 3 22:11:07 myhost postgres[1918]: [4] LOG: next transaction id: > 1090597972; next oid: 4231750970 >=20 > Mar 3 22:11:07 myhost postgres[1918]: [5] LOG: database system was > not properly shut down; automatic recovery in progress >=20 > Mar 3 22:11:07 myhost postgres[1918]: [6] LOG: redo starts at > 1ABC/9044F3B4 >=20 > Mar 3 22:11:07 myhost postgres[1919]: [1] FATAL: The database system > is starting up >=20 > *** PG was up after a lot of the above message *** >=20 > =20 >=20 > PG version is 7.3.2 on Red Hat Enterprise Linux ES release 3 (Taroon > Update 4)=20 >=20 > I know it is old, but anyone can smell why PG shutdown itself? This sounds like postgresql ran up against the Out Of Memory killer in the linux kernel, but I thought it killed things with -9, which would result in an immediate shutdown. Maybe a ulimit issue? Those are the two most common causes of postgresql premature shutdown.