Postgres 9.1 and 9.2 crashing with exit code 9 - Mailing list pgsql-bugs
From | Tony Kurz |
---|---|
Subject | Postgres 9.1 and 9.2 crashing with exit code 9 |
Date | |
Msg-id | DBD2452DADA9F24286C985F92B31F988572536E8A5@EXMBOX5.hosting.inetserver.de Whole thread Raw |
List | pgsql-bugs |
Hello Guys I have following situation: PostgreSQL Database 9.1 32 Bit is crashing immediately, it's an Windows 200= 8R2. I have patched to 9.2 64Bit, but is crashing with the same Exit code What is "exit code 9"?? Here is an cut from the postgres.log 013-01-31 14:42:08 CETCONTEXT: automatic vacuum of table "cloud.public.m20= 1301_devicestatus"2013-01-31 14:43:14 CETLOG: server process (PID 5820) ex= ited with exit code 9 2013-01-31 14:43:14 CETLOG: terminating any other active server processes 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:14 CETWARNING: terminating connection because of crash of= another server process 2013-01-31 14:43:14 CETDETAIL: The postmaster has commanded this server pr= ocess to roll back the current transaction and exit, because another server= process exited abnormally and possibly corrupted shared memory. 2013-01-31 14:43:14 CETHINT: In a moment you should be able to reconnect t= o the database and repeat your command. 2013-01-31 14:43:15 CETLOG: all server processes terminated; reinitializin= g 2013-01-31 14:43:24 CETFATAL: pre-existing shared memory block is still in= use 2013-01-31 14:43:24 CETHINT: Check if there are any old server processes s= till running, and terminate them. We have an active antivirus scanner, but we excluding the PostgreSQL folder= s where are the data folder locate is. Hope any one can help Best regards Tony
pgsql-bugs by date: