Обсуждение: BUG #5965: PostgreSQL crashes during connection

Поиск
Список
Период
Сортировка

BUG #5965: PostgreSQL crashes during connection

От
"Daniel Migowski"
Дата:
The following bug has been logged online:

Bug reference:      5965
Logged by:          Daniel Migowski
Email address:      dmigowski@ikoffice.de
PostgreSQL version: 8.3.9
Operating system:   Windows 7
Description:        PostgreSQL crashes during connection
Details:

Hi,

My PostgreSQL server just crashed during an attempt to connect to it
(multiple times at once, a connection pool just started up).

These lines were found in the logfile afterwards:

2011-04-06 11:38:03 CEST [2860] LOG:  server process (PID 19812) was
terminated by exception 0xC000012D
2011-04-06 11:38:03 CEST [2860] HINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2011-04-06 11:38:03 CEST [2860] LOG:  terminating any other active server
processes
2011-04-06 11:38:03 CEST [12208] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [12208] 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.
2011-04-06 11:38:03 CEST [12208] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [23548] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [23548] 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.
2011-04-06 11:38:03 CEST [23548] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [24024] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [24024] 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.
2011-04-06 11:38:03 CEST [24024] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [120] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [120] 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.
2011-04-06 11:38:03 CEST [120] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [10948] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [10948] 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.
2011-04-06 11:38:03 CEST [10948] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [26172] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [26172] 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.
2011-04-06 11:38:03 CEST [26172] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [12176] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [12176] 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.
2011-04-06 11:38:03 CEST [12176] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [3420] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [3420] 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.
2011-04-06 11:38:03 CEST [3420] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [11184] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [11184] 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.
2011-04-06 11:38:03 CEST [11184] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [7664] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [7664] 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.
2011-04-06 11:38:03 CEST [7664] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [23716] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [23716] 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.
2011-04-06 11:38:03 CEST [23716] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [15424] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [15424] 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.
2011-04-06 11:38:03 CEST [15424] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [18384] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [18384] 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.
2011-04-06 11:38:03 CEST [18384] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [9272] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [9272] 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.
2011-04-06 11:38:03 CEST [9272] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [13448] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [13448] 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.
2011-04-06 11:38:03 CEST [13448] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:03 CEST [14496] WARNING:  terminating connection because of
crash of another server process
2011-04-06 11:38:03 CEST [14496] 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.
2011-04-06 11:38:03 CEST [14496] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2011-04-06 11:38:04 CEST [15020] LOG:  loaded library
"$libdir/plugins/plugin_debugger.dll"
2011-04-06 11:38:04 CEST [13480] LOG:  loaded library
"$libdir/plugins/plugin_debugger.dll"
2011-04-06 11:38:04 CEST [20124] LOG:  loaded library
"$libdir/plugins/plugin_debugger.dll"
2011-04-06 11:38:04 CEST [17376] LOG:  loaded library
"$libdir/plugins/plugin_debugger.dll"
2011-04-06 11:38:04 CEST [13480] LOG:  connection received:
host=helena.ikoffice.de port=58369
2011-04-06 11:38:04 CEST [20124] LOG:  connection received:
host=helena.ikoffice.de port=58371
2011-04-06 11:38:04 CEST [20124] FATAL:  the database system is in recovery
mode
2011-04-06 11:38:04 CEST [13480] FATAL:  the database system is in recovery
mode
2011-04-06 11:38:04 CEST [17376] LOG:  connection received:
host=helena.ikoffice.de port=58370
2011-04-06 11:38:04 CEST [17376] FATAL:  the database system is in recovery
mode
2011-04-06 11:38:04 CEST [2860] LOG:  all server processes terminated;
reinitializing
2011-04-06 11:38:04 CEST [2860] FATAL:  could not create shared memory
segment: 1455
2011-04-06 11:38:04 CEST [2860] DETAIL:  Failed system call was
CreateFileMapping(size=787668992, name=Global/PostgreSQL:C:/Program
Files/PostgreSQL/8.3/data).

I get these crashes occasionally, and don't know if they have been fixed in
a later version. Sorry for not using the bleeding edge version :).

Re: BUG #5965: PostgreSQL crashes during connection

От
Alvaro Herrera
Дата:
Excerpts from Daniel Migowski's message of mié abr 06 06:45:25 -0300 2011:

> PostgreSQL version: 8.3.9
> Operating system:   Windows 7

> My PostgreSQL server just crashed during an attempt to connect to it
> (multiple times at once, a connection pool just started up).
>
> These lines were found in the logfile afterwards:
>
> 2011-04-06 11:38:03 CEST [2860] LOG:  server process (PID 19812) was
> terminated by exception 0xC000012D

Upgrade to 8.3.14 and let us know how it goes.


> I get these crashes occasionally, and don't know if they have been fixed in
> a later version. Sorry for not using the bleeding edge version :).

No, that cannot be forgiven really.

--
Álvaro Herrera <alvherre@alvh.no-ip.org>

Re: BUG #5965: PostgreSQL crashes during connection

От
Robert Haas
Дата:
On Wed, Apr 6, 2011 at 12:14 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> w=
rote:
> Excerpts from Daniel Migowski's message of mi=E9 abr 06 06:45:25 -0300 20=
11:
>> PostgreSQL version: 8.3.9
>> Operating system: =A0 Windows 7
>
>> My PostgreSQL server just crashed during an attempt to connect to it
>> (multiple times at once, a connection pool just started up).
>>
>> These lines were found in the logfile afterwards:
>>
>> 2011-04-06 11:38:03 CEST [2860] LOG: =A0server process (PID 19812) was
>> terminated by exception 0xC000012D
>
> Upgrade to 8.3.14 and let us know how it goes.

If the crash is still happening on 8.3.14, then it would be helpful if
you could attempt to obtain a stack backtrace.

http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreS=
QL_backend_on_Windows

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company