Thread: BUG #5260: Postgre crashed unexpectedly

BUG #5260: Postgre crashed unexpectedly

From
"Toni Helenius"
Date:
The following bug has been logged online:

Bug reference:      5260
Logged by:          Toni Helenius
Email address:      toni.helenius@syncrontech.com
PostgreSQL version: 8.3.9
Operating system:   Windows 2008 Server Enterprise
Description:        Postgre crashed unexpectedly
Details:

Postgre database was running normally and several applications using it
normally like any other day. Then the Postge just died and didn't recover by
itself.. Here is the log:

2009-12-31 13:41:09 EET LOG:  server process (PID 7020) was terminated by
exception 0xC0000005
2009-12-31 13:41:09 EET HINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2009-12-31 13:41:09 EET LOG:  terminating any other active server processes
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING:  terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET LOG:  loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-12-31 13:41:09 EET FATAL:  the database system is in recovery mode
2009-12-31 13:41:10 EET LOG:  all server processes terminated;
reinitializing
2009-12-31 13:41:20 EET FATAL:  pre-existing shared memory block is still in
use
2009-12-31 13:41:20 EET HINT:  Check if there are any old server processes
still running, and terminate them.

Re: BUG #5260: Postgre crashed unexpectedly

From
Robert Haas
Date:
On Mon, Jan 4, 2010 at 5:29 AM, Toni Helenius
<toni.helenius@syncrontech.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05260
> Logged by: =A0 =A0 =A0 =A0 =A0Toni Helenius
> Email address: =A0 =A0 =A0toni.helenius@syncrontech.com
> PostgreSQL version: 8.3.9
> Operating system: =A0 Windows 2008 Server Enterprise
> Description: =A0 =A0 =A0 =A0Postgre crashed unexpectedly
> Details:
>
> Postgre database was running normally and several applications using it
> normally like any other day. Then the Postge just died and didn't recover=
 by
> itself.. Here is the log:
[...]
> 2009-12-31 13:41:20 EET FATAL: =A0pre-existing shared memory block is sti=
ll in
> use
> 2009-12-31 13:41:20 EET HINT: =A0Check if there are any old server proces=
ses
> still running, and terminate them.

Per the hint, did you check whether there are any old server processes
still running?

If you don't find any old server processes running, I would guess that
a reboot would likely be a good next step toward getting the system
back up.

Unfortunately I'm not sure what could have caused the original crash.

...Robert