X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 266F79FB56F for ; Fri, 25 Aug 2006 06:20:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 80469-02 for ; Fri, 25 Aug 2006 09:20:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 2B3C99FB570 for ; Fri, 25 Aug 2006 06:20:48 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id k7P9Kg5h098342 for ; Fri, 25 Aug 2006 06:20:42 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id k7P99NO1095655 for pgsql-admin@postgresql.org; Fri, 25 Aug 2006 06:09:23 -0300 (ADT) (envelope-from news) From: Volker X-Newsgroups: pgsql.admin Subject: Re: Server Down problem Date: Fri, 25 Aug 2006 11:13:41 +0200 Organization: Hub.Org Networking Services Lines: 33 Message-ID: References: <19002.1156343510@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.5 (Windows/20051201) In-Reply-To: <19002.1156343510@sss.pgh.pa.us> To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200608/275 X-Sequence-Number: 22818 Hi tom, the database is on a mountable volume. So that could be our problem. Reading your comments i would like to know if an automatic initdb on postmaster startup can be disabled. Is this possible? We would receive a severe postmaster error, but this would be expected behaviour in case that the mountable volume is temporarily unavailable. Volker > It looks to me like pg_control is quite out of sync with the files in > pg_xlog. pg_control claims to have checkpointed as recently as 16-Aug > but there is no file newer than 7-Aug in pg_xlog. The other thing that > is strange is that the filename numbers in pg_xlog correspond to WAL > locations much higher than what pg_control claims is the end of WAL. > > Is $PGDATA kept on a dismountable volume (ie, not the root disk)? > If so it might be a good idea to unmount the volume and look to see > if there's anything under the mount point. I recall having seen > corruption that came from trying to start Postgres before the $PGDATA > disk had been mounted --- the initscript happily initdb'd a new database > under the mount-point directory, and then when the main disk did come up > things were badly hosed because the server was working with a pg_control > in memory that was completely out of sync with everything else. This > looks a bit like that might have happened here. > > As far as running pg_resetxlog goes, there is advice about setting the > parameters in recent releases' documentation; try > http://developer.postgresql.org/docs/postgres/app-pgresetxlog.html > for the latest. (Some of the parameters mentioned don't exist in > 7.4; just ignore 'em.) I'm afraid though that you may have actual > database corruption. If so pg_resetxlog won't fix it.