Postgres Pro
Downloads
Home   >   mailing lists

Thread: Fatal error

Fatal error

From
mmiranda@americatel.com.sv
Date:
Hi , my server crashed this morning, aparently by a power failure, postgres
refeses to start, this is the boot log


LOG:  database system was interrupted being in recovery at 2005-04-29
14:10:43 CST
        This probably means that some data blocks are corrupted
        and you will have to use the last backup for recovery.
LOG:  checkpoint record is at F1/A0A4E05C
LOG:  redo record is at F1/A0A4E05C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 98967076; next oid: 151578857
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  redo starts at F1/A0A4E09C
PANIC:  Invalid page header in block 68122 of 17006
LOG:  startup process (pid 1959) was terminated by signal 6
LOG:  aborting startup due to startup process failure


What can i do to repair the DB, only dump/restore?, i hav  tried that, but
the dump file is 14G and linux redhat 7.3 complains with file too large.
suggestions?

thanks

Re: Fatal error

From
Tom Lane
Date:
mmiranda@americatel.com.sv writes:
> LOG:  redo starts at F1/A0A4E09C
> PANIC:  Invalid page header in block 68122 of 17006
> LOG:  startup process (pid 1959) was terminated by signal 6
> LOG:  aborting startup due to startup process failure

Which PG version is this exactly?  If it's not the very latest in its
release series, an in-place update to the latest might help --- because
this looks like several known-and-fixed issues ...

            regards, tom lane

Re: Fatal error

From
mmiranda@americatel.com.sv
Date:
Tom Lane wrote:
> mmiranda@americatel.com.sv writes:
>> LOG:  redo starts at F1/A0A4E09C
>> PANIC:  Invalid page header in block 68122 of 17006
>> LOG:  startup process (pid 1959) was terminated by signal 6
>> LOG:  aborting startup due to startup process failure
>
> Which PG version is this exactly?  If it's not the very latest in its
> release series, an in-place update to the latest might help ---
> because this looks like several known-and-fixed issues ...
>
>             regards, tom lane


Postgres 7.3, i will try the upgrade tonigth,
thanks

Re: Fatal error

From
Alvaro Herrera
Date:
On Fri, Apr 29, 2005 at 10:44:53PM -0600, mmiranda@americatel.com.sv wrote:
> Tom Lane wrote:
> > mmiranda@americatel.com.sv writes:
> >> LOG:  redo starts at F1/A0A4E09C
> >> PANIC:  Invalid page header in block 68122 of 17006
> >> LOG:  startup process (pid 1959) was terminated by signal 6
> >> LOG:  aborting startup due to startup process failure
> >
> > Which PG version is this exactly?  If it's not the very latest in its
> > release series, an in-place update to the latest might help ---
> > because this looks like several known-and-fixed issues ...
>
> Postgres 7.3, i will try the upgrade tonigth,

That doesn't answer the question though, because Tom wanted to know
which of 7.3, 7.3.1, 7.3.4 etc you are running.  (You also didn't answer
the same question when I asked you.)

In the spanish list however, he disclosed that this problem happened on
a shared storage system, which is used by two postmasters on different
machines controlled by a heartbeat system.  The main server was
accidentaly disconnected from power.  I told him that concurrent
postmasters were fatal, but he hasn't confirmed whether they actually
ran concurrently.

Good luck with the upgrade, though I advise you not to use the heartbeat
system until you have really debugged it to work the way you want it to.
(Or not use it at all, and run Slony-I or some such replication system
instead.)

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Es filósofo el que disfruta con los enigmas" (G. Coli)