Skip site navigation (1) Skip section navigation (2)

Postgres 8.3 crashing unexpectedly

From: "umashankar narayanan" <umashankar(at)graffiti(dot)net>
To: Pgsql Admin <pgsql-admin(at)postgresql(dot)org>
Subject: Postgres 8.3 crashing unexpectedly
Date: 2012-03-08 18:29:30
Message-ID: 20120308182930.223720@gmx.com (view raw or flat)
Thread:
Lists: pgsql-admin
Version : 8.3

 Below is the log from the server.

 -----------------------------------------------------------------------------------------------------------------------

 2012-03-07 11:57:20 EST LOG: server process (PID 5944) exited with exit code 128
 2012-03-07 11:57:20 EST LOG: terminating any other active server processes
 2012-03-07 11:57:20 EST WARNING: terminating connection because of crash of another server process
 2012-03-07 11:57:20 EST 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.
 2012-03-07 11:57:20 EST HINT: In a moment you should be able to reconnect to the database and repeat your command.
 2012-03-07 11:57:20 EST WARNING: terminating connection because of crash of another server process
 2012-03-07 11:57:20 EST 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.
 2012-03-07 11:57:20 EST HINT: In a moment you should be able to reconnect to the database and repeat your command.
 2012-03-07 11:57:20 EST WARNING: terminating connection because of crash of another server process
 2012-03-07 11:57:20 EST 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.
 2012-03-07 11:57:20 EST HINT: In a moment you should be able to reconnect to the database and repeat your command.

 some more repeat of the above WARNING, DETAIL, HINT messages and then the below


 2012-03-07 11:57:21 EST LOG: archiver process (PID 9600) exited with exit code 1
 2012-03-07 11:57:21 EST LOG: all server processes terminated; reinitializing
 2012-03-07 11:57:22 EST FATAL: pre-existing shared memory block is still in use
 2012-03-07 11:57:22 EST HINT: Check if there are any old server processes still running, and terminate them.


 -----------------------------------------------------------------------------------------------------------------------

 Thanks in advance!

pgsql-admin by date

Next:From: umashankar narayananDate: 2012-03-08 19:23:59
Subject: Re: Postgres server crashing unexpectedly.
Previous:From: Kevin GrittnerDate: 2012-03-08 18:25:34
Subject: Re: Postgres server crashing unexpectedly.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group