Skip site navigation (1) Skip section navigation (2)

Re: Help! PostgreSQL stuck at starting up after crash

From: Samuel Hwang <samuel(at)replicon(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: david(at)beechglen(dot)com, pgsql-admin(at)postgresql(dot)org
Subject: Re: Help! PostgreSQL stuck at starting up after crash
Date: 2012-01-19 22:43:38
Message-ID: CAOPCsHFYJ0-va3bpgBvb5LoW=YwAOyyU8zqi-uJPC5fsuxsLKA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
> just nothing happened after that and postgresql is stuck at
> starting up and not getting out of archive recovery mode.\

What do you base that on?  (copy/paste)

==> I have waited for at least 2 hours, but the database is still in
starting up state. In the mean time, there is not cpu/disk activities.

> at that time there is no cpu/disk activities and it seemed like
> it's waiting for something?

That looks like normal recovery.  I would expect it to be waiting
for clients to connect at that point.

What happens when you try to connect to the database after that
above has been logged?  (Copy/paste the psql command line and any
errors, please.)

==> when I tried to use psql to connect the db, I got

FATAL:  the database system is starting up

and it doesn't allow connection.

On Thu, Jan 19, 2012 at 10:16 AM, Kevin Grittner <
Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:

> Samuel Hwang <samuel(at)replicon(dot)com> wrote:
> > I don't know how to make sure if WAL logs corrupted.
> > At the end of the recovery in postgresql log I saw
> >
> > 2012-01-18 18:30:58.570 MST     3666 - LOG:  consistent recovery
> >   state reached at 56C/CD0AFE00
> > 2012-01-18 18:30:58.587 MST     3666 - LOG:  recovery stopping
> >   before abort of transaction 541802043, time 2012-01-18
> >   12:50:08.531615-07
> > 2012-01-18 18:30:58.587 MST     3666 - LOG:  redo done at
> >   56C/CD226C58
> > 2012-01-18 18:30:58.587 MST     3666 - LOG:  last completed
> >   transaction was at log time 2012-01-18 12:49:28.321605-07
> > 2012-01-18 18:30:58.589 MST     3666 - LOG:  selected new timeline
> >   ID: 2
> > 2012-01-18 18:30:59.187 MST     3666 - LOG:  archive recovery
> >   complete
> >
> > just nothing happened after that and postgresql is stuck at
> > starting up and not getting out of archive recovery mode.\
>
> What do you base that on?  (copy/paste)
>
> > at that time there is no cpu/disk activities and it seemed like
> > it's waiting for something?
>
> That looks like normal recovery.  I would expect it to be waiting
> for clients to connect at that point.
>
> What happens when you try to connect to the database after that
> above has been logged?  (Copy/paste the psql command line and any
> errors, please.)
>
> -Kevin
>



-- 

*Shian-Miin Samuel Hwang* | Software Developer | Phone 1-403-2626519 (ext.
276) | Fax 1-403-233-8046

*Replicon* | Hassle-Free Time & Expense Management Software - 7,300
Customers - 70 Countries
www.replicon.com | facebook <http://www.facebook.com/Replicon.inc> |
twitter<http://twitter.com/Replicon>|
blog <http://www.replicon.com/blog/> | contact
us<http://www.replicon.com/about_replicon/contact_us.aspx>

*We are hiring!* | search
jobs<http://tbe.taleo.net/NA2/ats/careers/searchResults.jsp?org=REPLICON&cws=1&act=sort&sortColumn=1&__utma=1.651918544.1299001662.1299170819.1299174966.10&__utmb=1.8.10.1299174966&__utmc=1&__utmx=-&__utmz=1.1299174985.10.3.utmcsr=google%7Cutmccn=%28organic%29%7Cutmcmd=organic%7Cutmctr=replicon%20careers&__utmv=1.%7C3=Visitor%20Type=Prospects=1,&__utmk=40578466>

In response to

pgsql-admin by date

Next:From: Samuel HwangDate: 2012-01-19 22:45:34
Subject: Re: Help! PostgreSQL stuck at starting up after crash
Previous:From: Bruce MomjianDate: 2012-01-19 22:12:02
Subject: Re: Can't get pg_upgrade work for 8.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group