SEO

#1 (**permalink**) 04-09-2008, 07:14 AM

I looked in the log again and sure enough I missed this immediately
before the WARNINGS:

PANIC: link from /data/database/pg_xlog/00000001000000D9 to
/data/database/pg_xlog/00000001000000E1 (initialization of log file 1,
segment 225) failed: No such file or directory
LOG: server process (pid 5748) was terminated by signal 6
LOG: terminating any other active server processes

Looks like a file system problem right?

Medora

>
> > WARNING: Message from PostgreSQL backend:
> > The Postmaster has informed me that some other backend
> > died abnormally and possibly corrupted shared memory.
>
> This is bad, but it's unrelated to the other message, and you didn't
> show us the message that it *is* related to.
>
> regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#2 (**permalink**) 04-09-2008, 07:14 AM

"Medora Schauer" <mschauer@fairfield.com> writes:
> I looked in the log again and sure enough I missed this immediately
> before the WARNINGS:

> PANIC: link from /data/database/pg_xlog/00000001000000D9 to
> /data/database/pg_xlog/00000001000000E1 (initialization of log file 1,
> segment 225) failed: No such file or directory

> Looks like a file system problem right?

Definitely seems like a can't-happen case. What file system are you
running Postgres on?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: fatal error in pg.log