Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush

Tom,

Thanks for the help
I was able to find pg_resetxlog in the path. Are there any precautions that I need to be aware of? Or I just don't have any choice?
I'd like to do pg_dump or pg_dumpall.

Should I do a pg_resetxlog $PGDATA?

Here is my pgcontrol info:
------------------------------------------------------------------
_control version number: 71
Catalog version number: 200101061
Database state: SHUTDOWNING
pg_control last modified: Tue Feb 2 08:19:14 2010
Current log file id: 2
Next log file segment: 249
Latest checkpoint location: 2/F8D581BC
Prior checkpoint location: 2/F8D49A34
Latest checkpoint's REDO location: 2/F8D581BC
Latest checkpoint's UNDO location: 0/0
Latest checkpoint's StartUpID: 210
Latest checkpoint's NextXID: 79276624
Latest checkpoint's NextOID: 4412280
Time of latest checkpoint: Tue Feb 2 06:50:48 2010
Database block size: 8192
Blocks per segment of large relation: 131072
LC_COLLATE: en_US
LC_CTYPE: en_US
---------------------------------------------------
In my pg_xlog directory, I've:
total 32808
-rw------- 1 postgres postgres 16777216 Feb 2 06:54 00000002000000F8
-rw------- 1 postgres postgres 16777216 Feb 1 10:51 00000002000000F9

------------------------------------------------
Thanks for any help.
Mary Y Wang

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, February 02, 2010 11:53 AM
To: Wang, Mary Y
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush

"Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com> writes:
> I'm having a bad day. My Postgresql has this error "FATAL 2: XLogFlush: request is not satisfied". I tried to follow the 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