Thread: Postgres 9.2.8 crash sporadically on Windows

On 04/07/2014 07:48 AM, Sofer, Yuval wrote:
> Hi,
>
> Postgres server (9.2.8) crash on Windows sporadically
>
> Usually it happens after machine reboot that we do, once in a day
>
> After ~4 minutes it crashes with this error in the log:
>
> 2014-04-06 08:08:01.069 GMTLOG:  server process (PID 5304) exited with
> exit code 0
>
> 2014-04-06 08:08:01.069 GMTLOG:  terminating any other active server
> processes
>
> 2014-04-06 08:08:01.833 GMTLOG:  all server processes terminated;
> reinitializing
>
> 2014-04-06 08:08:11.183 GMTFATAL:  pre-existing shared memory block is
> still in use
>
> 2014-04-06 08:08:11.183 GMTHINT:  Check if there are any old server
> processes still running, and terminate them.
>
> This is production, Please help!

Some more information is going to be needed.

1) What do the system/Postgres logs show when the system is shut down?

2) Have you checked to see if there are indeed old server processes
still running?

>
> *Yuval Sofer*



--
Adrian Klaver
adrian.klaver@aklaver.com

On 04/07/2014 07:48 AM, Sofer, Yuval wrote:
> Hi,
>
> Postgres server (9.2.8) crash on Windows sporadically
>
> Usually it happens after machine reboot that we do, once in a day
>
> After ~4 minutes it crashes with this error in the log:
>
> 2014-04-06 08:08:01.069 GMTLOG:  server process (PID 5304) exited with
> exit code 0
>
> 2014-04-06 08:08:01.069 GMTLOG:  terminating any other active server
> processes
>
> 2014-04-06 08:08:01.833 GMTLOG:  all server processes terminated;
> reinitializing
>
> 2014-04-06 08:08:11.183 GMTFATAL:  pre-existing shared memory block is
> still in use
>
> 2014-04-06 08:08:11.183 GMTHINT:  Check if there are any old server
> processes still running, and terminate them.
>
> This is production, Please help!

Should have explained my reasoning behind my previous questions. They
are motivated by a hunch that the shutdown procedure is not cleanly
stopping Postgres and that on start up there is a collision with
detritus left over from the shutdown. So the idea is to look at the tail
of the logs on the shutdown side for clues. Would not hurt to look at
the head of the same logs on start up to see if there are any complaints
before the server process exits.

>
> *Yuval Sofer*
>


--
Adrian Klaver
adrian.klaver@aklaver.com