Re: PostgreSQL crash with PANIC message - Mailing list pgsql-general

On 03/23/2016 11:43 AM, Moreno Andreo wrote:
> Hello,
>      a customer of ours has an old PC (CoreDuo, 4 GB RAM, Windows XP)
> that's running PostgreSQL. Yesterday PostgreSQL started crashing
> suddenly with the following log
>
> 2016-03-23 10:40:42 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:40:42 CET LOG:  could not fork new process for connection:
> unrecognized winsock error 10004
> 2016-03-23 10:40:43 CET LOG:  could not receive data from client:
> unrecognized winsock error 10055
> 2016-03-23 10:40:43 CET LOG:  unexpected EOF on client connection
> 2016-03-23 10:42:48 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:48 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:49 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:49 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:50 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:50 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:51 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:51 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:52 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:52 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:53 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:53 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:54 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:54 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:55 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:55 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:42:56 CET LOG:  CreateProcess call failed: unrecognized
> winsock error 10004 (error code 1450)
> 2016-03-23 10:42:56 CET LOG:  could not fork autovacuum worker process:
> unrecognized winsock error 10004
> 2016-03-23 10:43:24 CET LOG:  could not receive data from client:
> unrecognized winsock error 10055
> 2016-03-23 10:43:24 CET LOG:  unexpected EOF on client connection
> 2016-03-23 10:43:24 CET LOG:  could not receive data from client:
> unrecognized winsock error 10061
> 2016-03-23 10:43:24 CET LOG:  unexpected EOF on client connection
> 2016-03-23 10:43:27 CET LOG:  could not receive data from client:
> unrecognized winsock error 10055
> 2016-03-23 10:43:27 CET LOG:  unexpected EOF on client connection
> 2016-03-23 10:43:30 CET PANIC:  could not write to log file 6, segment
> 217 at offset 3366912, length 8192: Invalid argument
>
> The machine has 4,5 GB of allocated memory (thus swapping).
> I googled to get some references to what's above and that's results:
> Winsock 10004 means Interrupted function call;
> Error code 1450 should mean "Insufficient system resources exist to
> complete the requested service"
> Winsock 10055 means "No buffer space available"
> Winsock 10061 means "Connection refused"
> The only thing I couldn't get some serious reference was the PANIC
> message that's in the last row.
>
> But putting the other things together, I figured out the machine is too
> obsolete and ran out of system resources, causing error 1450, which
> Winsock 10055 is solely a consequence, and probably the PANIC is
> generated by this mess.
>
> Am I right?

Might help to look in:

Control Panel --> Administrative Tools --> Event Viewer



>
> Thanks in advance,
> Moreno.
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com