pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedCrash logs (was RE: full data disk -- any chance of recovery )
2+ messages / 2 participants
[nested] [flat]
* Crash logs (was RE: full data disk -- any chance of recovery )
@ 2006-01-07 13:56 Gregory S. Williamson <gsw@globexplorer.com>
2006-01-07 17:41 ` Re: Crash logs (was RE: full data disk -- any chance of recovery ) Michael Fuhr <mike@fuhr.org>
0 siblings, 1 reply; 2+ messages in thread
From: Gregory S. Williamson @ 2006-01-07 13:56 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Jim C. Nasby <jnasby@pervasive.com>; +Cc: Tomaz Borstnar <tomaz.borstnar@over.net>; pgsql-admin
Back in the way-back Tom Lane wrote:
>
> Actually, as a developer I would've first wanted to look into the core
> files and try to see why they showed up in the first place. A gdb stack
> trace would often tell something useful (... if not to you, then to
> someone on the -hackers list ...). Cleaning up after a problem is fine,
> but don't destroy the evidence until you've learned as much as you can
> towards preventing the problem from happening again.
Well, I have a few core files:
[postgres@pgdb-05 138602992]$ !ls
ls -lt core*
-rw------- 1 postgres gxadmin 13897603 Jan 6 17:04 core.19845.gz
-rw------- 1 postgres gxadmin 24929043 Jan 6 17:02 core.18841.gz
-rw------- 1 postgres gxadmin 17264683 Jan 4 17:15 core.18996.gz
-rw------- 1 postgres gxadmin 5949066 Jan 4 17:13 core.17007.gz
-rw------- 1 postgres gxadmin 24513490 Jan 4 17:12 core.15891.gz
-rw------- 1 postgres gxadmin 24830413 Jan 4 16:38 core.11317.gz
I can probably find a way to put them on our site for ftp retrieval next week, if there is any interest.
It a tribute to postgres that there are so many, so close in time !
Well, ok, it is bad there are crashes but this 7.4 with an early postGIS version (which I think is the real problem -- I will bet that we see far fewer crashes with current releases, especially in the postGIS side o' things). But I've seen other databases crash and either need a manual restart or even a reboot of the afflicted server, and then a while to recover. Admittedly, this database is a read-only DB with few but large updates. Still -- 2 minutes to recover and be fatally slain again !! That's wicked fast.
Appended below is a snippet from logs for a recent crash (no outside intervention so whatver signals are sent are either postgres or linux):
But like I've said, I am reasonably certain that 8.1/postGIS 1.0 will be better and I don't want to waste anyone's time chasing after bugs that may have already been swatted.
Cheers,
Greg Williamson
DBA
GlobeXplorer LLC
Log:
2006-01-06 17:02:22 NOTICE: AssertionFailedException: Should never reach here: Unknown Precision Model type encountered
2006-01-06 17:02:22 ERROR: GEOS Intersection() threw an error!
2006-01-06 17:02:23 NOTICE: IllegalArgumentException: LinearRing not closed
2006-01-06 17:02:23 ERROR: Couldnt convert the postgis geometry to GEOS!
2006-01-06 17:02:23 NOTICE: IllegalArgumentException: LinearRing not closed
2006-01-06 17:02:23 ERROR: Couldnt convert the postgis geometry to GEOS!
2006-01-06 17:02:25 LOG: server process (PID 18841) was terminated by signal 11
2006-01-06 17:02:25 LOG: terminating any other active server processes
2006-01-06 17:02:25 WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Crash logs (was RE: full data disk -- any chance of recovery )
2006-01-07 13:56 Crash logs (was RE: full data disk -- any chance of recovery ) Gregory S. Williamson <gsw@globexplorer.com>
@ 2006-01-07 17:41 ` Michael Fuhr <mike@fuhr.org>
0 siblings, 0 replies; 2+ messages in thread
From: Michael Fuhr @ 2006-01-07 17:41 UTC (permalink / raw)
To: Gregory S. Williamson <gsw@globexplorer.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Jim C. Nasby <jnasby@pervasive.com>; Tomaz Borstnar <tomaz.borstnar@over.net>; pgsql-admin
On Sat, Jan 07, 2006 at 05:56:33AM -0800, Gregory S. Williamson wrote:
> But like I've said, I am reasonably certain that 8.1/postGIS 1.0 will
> be better and I don't want to waste anyone's time chasing after bugs
> that may have already been swatted.
The PostGIS developers have fixed a lot of crash-causing bugs in
the last few months, so definitely try a current version. You might
also want to upgrade GEOS.
--
Michael Fuhr
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2006-01-07 17:41 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-01-07 13:56 Crash logs (was RE: full data disk -- any chance of recovery ) Gregory S. Williamson <gsw@globexplorer.com>
2006-01-07 17:41 ` Michael Fuhr <mike@fuhr.org>
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