From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | "Sofer, Yuval" <Yuval_Sofer(at)bmc(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.2.8 crash sporadically on Windows |
Date: | 2014-04-07 15:15:32 |
Message-ID: | 18921.1396883732@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-04-07 09:49:09 -0500, Sofer, Yuval wrote:
>> Postgres server (9.2.8) crash on Windows sporadically
>> 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!
> This is unfortunately not giving us many details to work with...
The "exit code 0" bit reminds me of this:
http://www.postgresql.org/message-id/21027.1393546453@sss.pgh.pa.us
Is there another exit report for the same PID just above the quoted log
extract? Because if there isn't, the postmaster shouldn't be thinking
that status 0 represents a crash.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-04-07 15:20:25 | Re: Postgres 9.2.8 crash sporadically on Windows |
Previous Message | Andres Freund | 2014-04-07 14:52:02 | Re: Postgres 9.2.8 crash sporadically on Windows |