Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 35FF29FB3D6 for ; Fri, 27 Jul 2007 14:47:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 01674-02 for ; Fri, 27 Jul 2007 14:47:11 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by postgresql.org (Postfix) with ESMTP id E7E359FB3CD for ; Fri, 27 Jul 2007 14:47:10 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 68so560978wri for ; Fri, 27 Jul 2007 10:47:10 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=WBd8sQxuYqysWouuCWyWenVhYSVXUtR2YMM4QwyoVMFrWg3IQuPvJH8C/9+ktV5DbLRU334uf1arbAEjrpVBhI5LuwLS5QOO8D+EG58AvN7JNATnnNC5w/tTGdwy1VgaEAJyAf2aNR86r1eg0J8pUk39CEj58OFNx7imucXg18Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=NFtNBXE7tzt3gp5DMUX8lt5LczQJp/EnTChKGmQdVgzEbaDH8OJjmYpVth1hSeSJu+ye2FPXThXBrm7ac0j/GePImJ77+3ax9DI73gfXnPepJpo6GpUFaJiueHkzgUx393PDrWoJEno7QdqojLcF3q3Xl65rdoyyz+XuYuCgcC0= Received: by 10.78.205.7 with SMTP id c7mr808176hug.1185558429149; Fri, 27 Jul 2007 10:47:09 -0700 (PDT) Received: by 10.78.201.16 with HTTP; Fri, 27 Jul 2007 10:47:09 -0700 (PDT) Message-ID: <1d219a6f0707271047p1e20a7c0sb9bfc0a5ae24905d@mail.gmail.com> Date: Fri, 27 Jul 2007 13:47:09 -0400 From: "Chris Hoover" To: "Tena Sakai" Subject: Re: my postgres is dead. need help! Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6908_13127969.1185558429126" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/316 X-Sequence-Number: 26297 ------=_Part_6908_13127969.1185558429126 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/27/07, Tena Sakai wrote: > > Hi folks, > > My postgres (v 7.1.4, I think) did not come up upon reboot. > I have tried to use startup script called postgresql in > /etc/rc.d/init.d directory, but it reports FATAL when I > try to stop postmaster. > > The most recent log file in /pgsql/data/pg_log reads: > > LOG: database system was interrupted while in recovery at 2007-07-27 > 08:30:34 PDT > HINT: This probably means that some data is corrupted and you will have > to use the last backup for recovery. > LOG: checkpoint record is at 1F8/DB354F24 > LOG: redo record is at 1F8/D6060064; undo record is at 0/0; shutdown > FALSE > LOG: next transaction ID: 700570822; next OID: 2763554 > LOG: next MultiXactId: 3; next MultiXactOffset: 6 > LOG: database system was not properly shut down; automatic recovery in > progress > LOG: redo starts at 1F8/D6060064 > FATAL: the database system is starting up > > I am totally lost what I need to do. > Help and ssistance highly appreciated. > > Regards, > > Tena Sakai > tsakai@gallo.ucsf.edu > The database has gone into recovery mode, and is trying to clean itself up. Just let it alone and monitor the logs. If all goes well, it will tell you the recovery completed and it is online. Chris P.S. You are in desperate need of upgrading to a newer version of Postgres. ------=_Part_6908_13127969.1185558429126 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 7/27/07, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:

Hi folks,

My postgres (v 7.1.4, I think) did not come up upon reboot.
I have tried to use startup script called postgresql in
/etc/rc.d/init.d directory, but it reports FATAL when I
try to stop postmaster.

The most recent log file in /pgsql/data/pg_log reads:

LOG:  database system was interrupted while in recovery at 2007-07-27 08:30:34 PDT
HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG:  checkpoint record is at 1F8/DB354F24
LOG:  redo record is at 1F8/D6060064; undo record is at 0/0; shutdown FALSE
LOG:  next transaction ID: 700570822; next OID: 2763554
LOG:  next MultiXactId: 3; next MultiXactOffset: 6
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  redo starts at 1F8/D6060064
FATAL:  the database system is starting up

I am totally lost what I need to do.
Help and ssistance highly appreciated.

Regards,

Tena Sakai
tsakai@gallo.ucsf.edu

The database has gone into recovery mode, and is trying to clean itself up.  Just let it alone and monitor the logs.  If all goes well, it will tell you the recovery completed and it is online.

Chris

P.S.

You are in desperate need of upgrading to a newer version of Postgres. 
------=_Part_6908_13127969.1185558429126--