Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush - Mailing list pgsql-admin

From Tom Lane
Subject Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Date
Msg-id 29452.1265140359@sss.pgh.pa.us
Whole thread Raw
In response to Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
Responses Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
List pgsql-admin
"Wang, Mary Y" <mary.y.wang@boeing.com> writes:
> I'm having a bad day. My Postgresql has this error "FATAL 2:  XLogFlush: request is not satisfied".   I tried to
followthe instructions from a thread about looking for a core dump, but when I tried to start the postmaster, I got
"/usr/bin/postmaster:Startup proc 30595 exited with status 512 - abort". 

You've got a corrupted page that is affected by a WAL replay operation,
so things are pretty much a mess.

> I'm pg version is postgresql-7.1.3-2.  What are my options?

[ blanches... ]  You do realize that that version has been obsolete
since 2002?

pg_resetxlog was a contrib module in 7.1, so if you can find the
software repository you got postgresql from, you should be able to
install postgresql-contrib.  However, I am betting this thing is so
old that you don't even have the chance at doing that.

Most likely you're going to have to go back to your last backup.
After which, you should make it a priority to get onto a less
antique version of Postgres (and the underlying OS too, no doubt).

            regards, tom lane

pgsql-admin by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Using pg_migrator to upgrade 8.3->8.4
Next
From: "Wang, Mary Y"
Date:
Subject: Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush