Thread: repeatedly process termination in PG 8.2
Hi there,
one of our systems on a PG 8.2 database crashes nearly daily; others are running fine. Host OS of this system is
Windows,if the db crashes nothing is written in the OS event logs. The database log show every time the following
messages:
2009-09-23 10:21:30 LOG: server process (PID 1240) exited with exit code -1073741819
2009-09-23 10:21:30 LOG: terminating any other active server processes
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process
2009-09-23 10:21:30 DETAIL: The postmaster has commanded this server process to roll back the current
transactionand exit, because another server process exited abnormally and possibly corrupted shared memory.
2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2009-09-23 10:21:32 LOG: all server processes terminated; reinitializing
The exit code in the first log line is the same on every crash even. But I could not find anything about it on the net.
Otherapplications on the same system doesn´t show notes that reference to hardware based causes. May anyone give me a
hintwhat´s wrong with this system or what we can do to avoid further crashes?
Regards
Michael
--
Diese Mail wurde auf Viren geprüft mit Hilfe von Astaro Mail Gateway. http://www.astaro.com
On Thu, Sep 24, 2009 at 10:31 AM, Michael Molz <michael.molz@iwm-software.de> wrote: > one of our systems on a PG 8.2 database crashes nearly daily; others are running fine. Host OS of this system is Windows,if the db crashes nothing is written in the OS event logs. The database log show every time the following messages: > 2009-09-23 10:21:30 LOG: server process (PID 1240) exited with exit code -1073741819 > 2009-09-23 10:21:30 LOG: terminating any other active server processes > 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process Your symptoms point to one of two possibilities: 1) you have hardware faults or 2) your DB on this one machine has a corruption that causes postgres to try to read some absurd value of a pointer, causing a panic error. However, since nothing is logged in the postgres log complaining about bad pointers or something similar to that, I'd vote you have a hardware fault. One thing you can do to test your DB is to run vacuum full on it. If this produce no errors, try reindexing your tables. This causes every single row to be read which would throw an error if the table was corrupted. Of course, on reindex you could just clear your problem if an index itself was corrupted. If you do get an error during either of these steps, you should reboot, then re-run the same command to see if the error is in the exact same place every time. If not, then that would be a very strong indicator of hardware fault. Run your machine hardware diagnostics. If still nothing comes up, replace the machine. :-(