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

Re: Cannot start PostgreSQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Reinhard Hnat" <hnat(at)logotronic(dot)co(dot)at>
Cc: "Postgres Novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Cannot start PostgreSQL
Date: 2004-09-28 14:04:26
Message-ID: 14172.1096380266@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
"Reinhard Hnat" <hnat(at)logotronic(dot)co(dot)at> writes:
> DBAdmin(at)linuxtest:~> postgres -D $PGDATA
> LOG:  database system was shut down at 2004-09-07 11:15:03 CEST
> LOG:  open of /home/DBAdmin/postgres/data/pg_xlog/000000010000003E (log file
> 1, segment 62) failed: Datei oder Verzeichnis nicht gefunden
> LOG:  invalid primary checkpoint record
> LOG:  open of /home/DBAdmin/postgres/data/pg_xlog/000000010000003E (log file
> 1, segment 62) failed: Datei oder Verzeichnis nicht gefunden
> LOG:  invalid secondary checkpoint record
> PANIC:  unable to locate a valid checkpoint record

> The files noted in the above messages do not exist but there are otheres
> called 0000000100000078 .. 000000010000007D

Did you suffer some kind of system crash?  xlog files don't normally
just disappear.

You can probably get out of this with pg_resetxlog.  I'm not sure
whether you will find corrupted data after you do.  The log messages
seem to indicate that the database had been shut down cleanly before
the problem occurred; if so the contents of xlog aren't really needed.
But if you had filesystem corruption it may have affected more than
just the xlog files.  A dump and reload might be prudent.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Steve TucknottDate: 2004-09-28 14:25:18
Subject: pg_dump / pg_restore
Previous:From: Michael GuerinDate: 2004-09-28 12:38:33
Subject: Re: cache lookup failed for relation

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