Re: DB terminating [on Windows]

Magnus, any thoughts?

On Wed, Nov 18, 2009 at 9:53 AM, Scott Felt <scott(dot)felt(at)gmail(dot)com> wrote:
>
> Hello.  I have been having an issue with a database.  The logs consistently
> show this:
>
> 2009-11-17 16:03:55 ESTLOG:  00000: server process (PID 9644) exited with
> exit code 128
> 2009-11-17 16:03:55 ESTLOCATION:  LogChildExit,
> .\src\backend\postmaster\postmaster.c:2705
> 2009-11-17 16:03:55 ESTLOG:  00000: terminating any other active server
> processes
> 2009-11-17 16:03:55 ESTLOCATION:  HandleChildCrash,
> .\src\backend\postmaster\postmaster.c:2552
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:55 ESTWARNING:  57P02: terminating connection because of
> crash of another server process
> 2009-11-17 16:03:55 ESTDETAIL:  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-11-17 16:03:55 ESTHINT:  In a moment you should be able to reconnect to
> the database and repeat your command.
> 2009-11-17 16:03:55 ESTLOCATION:  quickdie,
> .\src\backend\tcop\postgres.c:2495
> 2009-11-17 16:03:57 ESTLOG:  00000: all server processes terminated;
> reinitializing
> 2009-11-17 16:03:57 ESTLOCATION:  PostmasterStateMachine,
> .\src\backend\postmaster\postmaster.c:2910
> 2009-11-17 16:04:07 ESTFATAL:  XX000: pre-existing shared memory block is
> still in use
> 2009-11-17 16:04:07 ESTHINT:  Check if there are any old server processes
> still running, and terminate them.
> 2009-11-17 16:04:07 ESTLOCATION:  PGSharedMemoryCreate,
> .\src\backend\port\win32_shmem.c:185
> 2009-11-17 16:04:08 ESTDEBUG:  00000: logger shutting down
> 2009-11-17 16:04:08 ESTLOCATION:  SysLoggerMain,
> .\src\backend\postmaster\syslogger.c:434
>
>
> Prior to this, the logs show nothing other than AutoVacWorkerMain
> activities.  This database is installed on a Windows OS.  The version of
> PostgreSQL is 8.4.1 (which I was hoping had a fix since I saw references to
> a bug fix for a shared memory problem).  Does anybody have any suggestions
> on how to determine what causes these shutdowns?  Should I be considering
> dialing up the shared_buffers size in the config file?  Currently it is set
> at 32mb.
>
> Thanks for any help.
>
> --
> View this message in context: http://old.nabble.com/DB-terminating-tp26412532p26412532.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug