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

Поиск
Список
Период
Сортировка
От Wang, Mary Y
Тема Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Дата
Msg-id FA20D4C4FEBFD148B1C0CB09913825FC01EBD52C6C@XCH-SW-06V.sw.nos.boeing.com
обсуждение исходный текст
Ответы Re: Startup proc 30595 exited with status 512 - abort and FATAL 2: XLogFlush
Список pgsql-admin
Hi,
I'm having a bad day. My Postgresql has this error "FATAL 2:  XLogFlush: request is not satisfied".   I tried to follow
theinstructions 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". 

How do I find the corrupted record?  If that is the case.

I'm pg version is postgresql-7.1.3-2.  What are my options?  I read some where that I can pg_resetxlog, but I can't
evenfind it in the path. 

This is from the log file:

********************************************************************************************************************************
DEBUG:  database system was shut down at 2010-02-01 19:24:40 PST
DEBUG:  CheckPoint record at (2, 4173828852)
DEBUG:  Redo record at (2, 4173828852); Undo record at (0, 0); Shutdown TRUE
DEBUG:  NextTransactionId: 79259759; NextOid: 4395896
DEBUG:  database system is in production state
Smart Shutdown request at Mon Feb  1 20:08:59 2010
DEBUG:  shutting down
DEBUG:  database system is shut down
DEBUG:  database system shutdown was interrupted at 2010-02-02 07:54:51 PST
DEBUG:  CheckPoint record at (2, 4174741948)
DEBUG:  Redo record at (2, 4174741948); Undo record at (0, 0); Shutdown FALSE
DEBUG:  NextTransactionId: 79276624; NextOid: 4412280
DEBUG:  database system was not properly shut down; automatic recovery in progress...
DEBUG:  redo starts at (2, 4174742012)
DEBUG:  ReadRecord: record with zero len at (2, 4174768976)
DEBUG:  redo done at (2, 4174768916)
FATAL 2:  XLogFlush: request is not satisfied
/usr/bin/postmaster: Startup proc 30708 exited with status 512 - abort
DEBUG:  database system shutdown was interrupted at 2010-02-02 08:11:50 PST
DEBUG:  CheckPoint record at (2, 4174741948)
DEBUG:  Redo record at (2, 4174741948); Undo record at (0, 0); Shutdown FALSE
DEBUG:  NextTransactionId: 79276624; NextOid: 4412280
DEBUG:  database system was not properly shut down; automatic recovery in progress...
DEBUG:  redo starts at (2, 4174742012)
DEBUG:  ReadRecord: record with zero len at (2, 4174768976)
DEBUG:  redo done at (2, 4174768916)
FATAL 2:  XLogFlush: request is not satisfied
/usr/bin/postmaster: Startup proc 30722 exited with status 512 - abort
DEBUG:  database system shutdown was interrupted at 2010-02-02 08:18:59 PST
DEBUG:  CheckPoint record at (2, 4174741948)
DEBUG:  Redo record at (2, 4174741948); Undo record at (0, 0); Shutdown FALSE
DEBUG:  NextTransactionId: 79276624; NextOid: 4412280
DEBUG:  database system was not properly shut down; automatic recovery in progress...
DEBUG:  redo starts at (2, 4174742012)
DEBUG:  ReadRecord: record with zero len at (2, 4174768976)
DEBUG:  redo done at (2, 4174768916)
FATAL 2:  XLogFlush: request is not satisfied
/usr/bin/postmaster: Startup proc 30788 exited with status 512 - abort
******************************************************************************************
Thanks in advance.
Mary

------------------------------------------------
Mary Y Wang



В списке pgsql-admin по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Issues with LC_COLLATE, across 8.3/8.4 on various platforms
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Using pg_migrator to upgrade 8.3->8.4