X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 7406C9DC80A for ; Tue, 14 Mar 2006 10:54:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 51272-01 for ; Tue, 14 Mar 2006 10:54:05 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by postgresql.org (Postfix) with ESMTP id 9DC629DC9DD for ; Tue, 14 Mar 2006 10:53:58 -0400 (AST) Received: by zproxy.gmail.com with SMTP id m7so2271184nzf for ; Tue, 14 Mar 2006 06:54:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=jd5pMuMgA3EC6yGDLI/cmQ7ipEYdQ7At2LZOifEQV51J0LtMx2/JDr+/rMzjjSQIK9b7Xwz4fhtdK6EpkpP3TWCqWhARmclf9F3ugLfyX0t0kYHof5IpEcdYrw6Z0nu7n1+HHFgrYMbFdOy/QHxrpGdhxU11yjCTlxKgSXDsFG8= Received: by 10.37.13.12 with SMTP id q12mr1591020nzi; Tue, 14 Mar 2006 06:54:01 -0800 (PST) Received: by 10.36.196.7 with HTTP; Tue, 14 Mar 2006 06:54:01 -0800 (PST) Message-ID: <68df54b40603140654j320d4298hc3cfca58f7993039@mail.gmail.com> Date: Tue, 14 Mar 2006 08:54:01 -0600 From: "Cory Vokey" To: pgsql-admin@postgresql.org Subject: Postgres process terminating MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19381_13517367.1142348041848" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.946 required=5 tests=[HTML_10_20=0.945, HTML_MESSAGE=0.001] X-Spam-Score: 0.946 X-Spam-Level: X-Archive-Number: 200603/115 X-Sequence-Number: 20872 ------=_Part_19381_13517367.1142348041848 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi all, I'm currently running postgres-7.4.12 with slony-1.0.5 and am seein= g the below postgres errors: Mar 14 00:00:25 master postgres[27357]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:25 master postgres[27357]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:25 master postgres[27356]: [17-1] LOG: 00000: unexpected pageaddr 1/55F4A000 in log file 1, segment 183, offset 16031744 Mar 14 00:00:25 master postgres[27356]: [17-2] LOCATION: ValidXLOGHeader, xlog.c:2096 Mar 14 00:00:25 master postgres[27356]: [18-1] LOG: 00000: redo done at 1/B7F49220 Mar 14 00:00:25 master postgres[27356]: [18-2] LOCATION: StartupXLOG, xlog.c:2796 Mar 14 00:00:26 master postgres[27386]: [11-1] LOG: 00000: connection received: host=3D172.20.42.19 port=3D54294 Mar 14 00:00:26 master postgres[27386]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27386]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:26 master postgres[27386]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:26 master postgres[27387]: [11-1] LOG: 00000: connection received: host=3D172.20.42.19 port=3D54295 Mar 14 00:00:26 master postgres[27387]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27387]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:26 master postgres[27387]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:26 master postgres[27388]: [11-1] LOG: 00000: connection received: host=3D172.20.42.20 port=3D38111 Mar 14 00:00:26 master postgres[27388]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27388]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:26 master postgres[27388]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:26 master postgres[27389]: [11-1] LOG: 00000: connection received: host=3D172.20.42.20 port=3D38112 Mar 14 00:00:26 master postgres[27389]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27389]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:26 master postgres[27389]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:26 master postgres[27392]: [11-1] LOG: 00000: connection received: host=3D172.20.42.19 port=3D54297 Mar 14 00:00:26 master postgres[27392]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27392]: [12-1] FATAL: 57P03: the database system is starting up Mar 14 00:00:26 master postgres[27392]: [12-2] LOCATION: ProcessStartupPacket, postmaster.c:1437 Mar 14 00:00:26 master postgres[27393]: [11-1] LOG: 00000: connection received: host=3D172.20.42.19 port=3D54298 Mar 14 00:00:26 master postgres[27393]: [11-2] LOCATION: BackendFork, postmaster.c:2395 Mar 14 00:00:26 master postgres[27393]: [12-1] FATAL: 57P03: the database system is starting up This causes slony to die on all clusters as well as our web applications. In google'ing for "FATAL: 57P03: the database system is starting up" I noticed other people having similar issues but I not been able to locate a fix. This morning I dropped all slony schema's from the database and am continuing to re-create my clusters one by one and have not seeing these errors thus far. What I am interested in is a description of the above error log. Any help is appreciated! Thanks. -- Cory Vokey ------=_Part_19381_13517367.1142348041848 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi all, I'm currently running postgres-7.4.12 with slony-1.0.5 and am seein= g the below postgres errors:

Mar 14 00:00:25 master postgres[27357]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:25 master postgres[27357]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:25 master postgres[27356]: [17-1] LOG:  00000: unexpected pageaddr 1/55F4A000 in log file 1, segment 183, offset 16031744
Mar 14 00:00:25 master postgres[27356]: [17-2] LOCATION:  ValidXLOGHea= der, xlog.c:2096
Mar 14 00:00:25 master postgres[27356]: [18-1] LOG:  00000: redo done = at 1/B7F49220
Mar 14 00:00:25 master postgres[27356]: [18-2] LOCATION:  StartupXLOG,= xlog.c:2796
Mar 14 00:00:26 master postgres[27386]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.19 port=3D5= 4294
Mar 14 00:00:26 master postgres[27386]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27386]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:26 master postgres[27386]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:26 master postgres[27387]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.19 port=3D5= 4295
Mar 14 00:00:26 master postgres[27387]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27387]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:26 master postgres[27387]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:26 master postgres[27388]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.20 port=3D3= 8111
Mar 14 00:00:26 master postgres[27388]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27388]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:26 master postgres[27388]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:26 master postgres[27389]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.20 port=3D3= 8112
Mar 14 00:00:26 master postgres[27389]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27389]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:26 master postgres[27389]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:26 master postgres[27392]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.19 port=3D5= 4297
Mar 14 00:00:26 master postgres[27392]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27392]: [12-1] FATAL:  57P03: the data= base system is starting up
Mar 14 00:00:26 master postgres[27392]: [12-2] LOCATION:  ProcessStart= upPacket, postmaster.c:1437
Mar 14 00:00:26 master postgres[27393]: [11-1] LOG:  00000: connection= received: host=3D172.20.42.19 port=3D5= 4298
Mar 14 00:00:26 master postgres[27393]: [11-2] LOCATION:  BackendFork,= postmaster.c:2395
Mar 14 00:00:26 master postgres[27393]: [12-1] FATAL:  57P03: the data= base system is starting up

This causes slony to die on all clusters as well as our web applications.
In google'ing for "FATAL:  57P03: the database system is starting up" I noticed other people having similar issues but I not been able t= o locate a fix.

This morning I dropped all slony schema's  from the database and am continuing to re-create my clusters one by one and have not seeing these errors thus far.

What I am interested in is a description of the above error log.

Any help is appreciated! 

Thanks.


--
Cory Vokey ------=_Part_19381_13517367.1142348041848--