pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedFatal error
2+ messages / 2 participants
[nested] [flat]
* Fatal error
@ 2002-09-04 03:44 Jean-Denis Girard <jd-girard@esoft.pf>
0 siblings, 1 reply; 2+ messages in thread
From: Jean-Denis Girard @ 2002-09-04 03:44 UTC (permalink / raw)
To: pgsql-interfaces
Hi,
Last tuesday I upgraded a production DB from 7.1 to 7.2.
Everything seemed fine till saturday, nightly vacuum exited with:
Debut: Sat Aug 31 04:00:01 TAHT 2002
FATAL 2: open of /var/lib/pgsql/data/pg_clog/0323 failed: No such file
or directory
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
connection to server was lost
Fin: Sat Aug 31 04:01:03 TAHT 2002
-*-*-*-
Debut: Sun Sep 1 04:00:00 TAHT 2002
FATAL 2: open of /var/lib/pgsql/data/pg_clog/027E failed: No such file
or directory
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
connection to server was lost
Fin: Sun Sep 1 04:00:32 TAHT 2002
The files actually do not exist.
After "truncating" (not "dropping") the offending table and reloading
it, the error disappeared.
This is a Linux system, with stock 2.4.18 kernel; no other problem on
the system (public web server).
/var/lib/pgsql is on its on Reiserfs partition, with plenty of room left.
Database is mainly accessed trough Perl-DBI + DBD-Pg-1.13.
No other component except Postgres and DBD-Pg were updated last week.
Don't know what to do and any help will be welcome. I can also provide
more specific information if needed.
--
Jean-Denis Girard
====================================================
Essential Software - Ingénierie Informatique
Solutions Linux & Open Source en Polynésie française
----------------------------------------------------
http://www.esoft.pf/
Tél: (689) 50 82 89
====================================================
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Fatal error
@ 2002-09-04 04:30 Tom Lane <tgl@sss.pgh.pa.us>
parent: Jean-Denis Girard <jd-girard@esoft.pf>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2002-09-04 04:30 UTC (permalink / raw)
To: Jean-Denis Girard <jd-girard@esoft.pf>; +Cc: pgsql-interfaces
Jean-Denis Girard <jd-girard@esoft.pf> writes:
> Last tuesday I upgraded a production DB from 7.1 to 7.2.
7.2? I'd hope you went to 7.2.2, or at least 7.2.1.
> FATAL 2: open of /var/lib/pgsql/data/pg_clog/0323 failed: No such file
> or directory
This message implies a bad xmin or xmax field in a stored tuple. We've
seen a number of reports of similar failures, but so far the evidence
has pointed to hardware failures rather than a software problem ---
corrupted data on disk would usually trigger this kind of failure before
anything else, so the particular error message doesn't seem very
significant.
> Don't know what to do and any help will be welcome. I can also provide
> more specific information if needed.
You should probably first try some hardware diagnostics like "memtest86"
and "badblocks".
I don't want to sound like I'm dismissing the possibility that it's a
Postgres bug. It could be ... but without more evidence there's not
much I can do to poke into it.
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2002-09-04 04:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-09-04 03:44 Fatal error Jean-Denis Girard <jd-girard@esoft.pf>
2002-09-04 04:30 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox