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 339BA11F696A for ; Thu, 30 Mar 2006 13:13:05 -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 14255-07 for ; Thu, 30 Mar 2006 13:13:03 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 1843211F694D for ; Thu, 30 Mar 2006 13:13:00 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Thu, 30 Mar 2006 17:12:59 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 30 Mar 2006 11:12:59 -0600 Subject: Re: Postgresql server does not start!:( -Re: PostgreSQl From: Scott Marlowe To: Chris Travers Cc: lmyho , Tom Lane , pgsql-admin@postgresql.org In-Reply-To: <442C10F1.2060005@metatrontech.com> References: <20060330165846.93504.qmail@web30813.mail.mud.yahoo.com> <442C10F1.2060005@metatrontech.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1143738779.26940.24.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 30 Mar 2006 11:12:59 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.139 required=5 tests=[AWL=0.138, MANY_EXCLAMATIONS=0, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.139 X-Spam-Level: X-Archive-Number: 200603/381 X-Sequence-Number: 21138 On Thu, 2006-03-30 at 11:10, Chris Travers wrote: > lmyho wrote: > > > > >The last one (successful bootup and shutdown): > >pg_log# more postgresql-2006-03-30_103237.log > >2006-03-30 10:32:37 CSTLOG: database system was shut down at 2006-03-30 10:32:20 > >CST > >2006-03-30 10:32:37 CSTLOG: checkpoint record is at 0/33B96C > >2006-03-30 10:32:37 CSTLOG: redo record is at 0/33B96C; undo record is at 0/0; > >shutdown TRUE > >2006-03-30 10:32:37 CSTLOG: next transaction ID: 5839; next OID: 16386 > >2006-03-30 10:32:37 CSTLOG: next MultiXactId: 1; next MultiXactOffset: 0 > >2006-03-30 10:32:37 CSTLOG: database system is ready > >2006-03-30 10:32:37 CSTLOG: transaction ID wrap limit is 2147484146, limited by > >database "postgres" > >2006-03-30 10:32:37 CSTLOG: autovacuum: processing database "template1" > >2006-03-30 10:33:37 CSTLOG: autovacuum: processing database "postgres" > >2006-03-30 10:33:42 CSTLOG: incomplete startup packet > >2006-03-30 10:33:42 CSTLOG: received fast shutdown request > >2006-03-30 10:33:42 CSTLOG: shutting down > >2006-03-30 10:33:42 CSTLOG: database system is shut down > >2006-03-30 10:33:42 CSTLOG: logger shutting down > > > >You can see they all have that line! Can you see what's may be the problem? Thank > >you!!! > > > > > Interesting.... Database starts up at 10:32:37 and processes all > databases through autovacuum. > Then exactly a minute later, it processes the postgres database. > 5 seconds later, you get a SIGINT. > > Is there something wrong with autovacuum? Normally I would doubt it but > the other possibility is something is waiting for just over a minute and > then shutting down the database. > > If you su postgres, can you run pg_ctl and get the database up by itself? If I remember correctly, this is a problem with the debian startup script requiring trust for the postgres superuser, and was discussed sometime last year. I'll wander through the archives in a free moment and see if I can find it.