Re: PANIC: could not locate a valid checkpoint record

Apparently the machine hung in between those two times.

I don't have any specific information, I am debugging remotely over
the phone.

Dave
On 16-Nov-05, at 5:21 PM, Tom Lane wrote:

> Dave Cramer <pg(at)fastcrypt(dot)com> writes:
>> Nov 16 18:03:32 dx1-ptr postgres[23410]: [4-1] LOG: shutting down
>> Nov 16 18:03:35 dx1-ptr postgres[23410]: [5-1] LOG: database system
>> is shut down
>> Nov 16 18:21:18 dx1-ptr postgres[10884]: [1-1] LOG: could not create
>> IPv6 socket: Address family not supported by protocol
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [2-1] LOG: database system
>> was shut down at 2005-11-16 18:03:35 GMT
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [3-1] LOG: could not open
>> file "/data/db/pgdata/pg_xlog/00000082000000E2" (log file 130, segm
>> ent 226): No such file or directory
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [4-1] LOG: invalid primary
>> checkpoint record
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [5-1] LOG: could not open
>> file "/data/db/pgdata/pg_xlog/00000082000000E2" (log file 130, segm
>> ent 226): No such file or directory
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [6-1] LOG: invalid
>> secondary checkpoint record
>> Nov 16 18:21:18 dx1-ptr postgres[10960]: [7-1] PANIC: could not
>> locate a valid checkpoint record
>
> So what happened between 18:03 and 18:21 exactly? If you don't have
> 00000082000000E2, what files *do* you have in pg_xlog? What does
> pg_controldata print?
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>