|
Hi, We’re using postgresql-8.3.5-1. Lately, once in a while, the PostgreSQL service crashes and
the following appears in the log. Any idea what could cause that? I believe there are two problems here: one is the process
2604 exiting with code 128, and the other one is the re-initialization failure
with the following fatal message: “BST FATAL: pre-existing shared memory
block is still in use”. 2009-05-27 10:39:41
BST LOG: server process (PID 2604) exited with exit code 128 2009-05-27 10:39:41
BST LOG: terminating any other active server processes 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST WARNING: terminating connection because of crash of another server process 2009-05-27 10:39:41
BST 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. 2009-05-27 10:39:41
BST HINT: In a moment you should be able to reconnect to the database and
repeat your command. 2009-05-27 10:39:41
BST LOG: all server processes terminated; reinitializing 2009-05-27 10:39:42
BST FATAL: pre-existing shared memory block is still in use 2009-05-27 10:39:42
BST HINT: Check if there are any old server processes still running, and
terminate them. Thanks, Moshe. The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ |
