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

Re: Postgres server crashing unexpectedly.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "umashankar narayanan" <umashankar(at)graffiti(dot)net>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgres server crashing unexpectedly.
Date: 2012-03-08 18:25:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"umashankar narayanan" <umashankar(at)graffiti(dot)net> wrote:
> Version : 8.3
Please give the full version and a bit more information about the
environment it's running in:
>  2012-03-07 11:57:20 EST LOG: server process (PID 5944) exited
> with exit code 128
Was there anything in the PostgreSQL log ahead of this to give a
clue what went wrong and caused this?  Is there anything in any of
system logs from around this time?
>  2012-03-07 11:57:20 EST LOG: terminating any other active server
> processes
This is normal -- when one process crashes this hard, it can leave
shared memory in a corrupted state, so PostgreSQL restarts to get a
clean environment with minimal down time.
> [each client process logging its termination] 

>  2012-03-07 11:57:21 EST LOG: all server processes terminated; 
> reinitializing
OK, it's trying to restart so clients can re-connect and continue.
>  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.
Something is still hanging on to the PostgreSQL shared memory block.
Are any postgres processes lingering?  Are you running anything else
which might be grabbing the same shared memory block?

pgsql-admin by date

Next:From: umashankar narayananDate: 2012-03-08 18:29:30
Subject: Postgres 8.3 crashing unexpectedly
Previous:From: Kevin GrittnerDate: 2012-03-08 17:06:02
Subject: Re: Postgres server crashing unexpectedly.

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