BUG #14246: Postgres crashing frequently

From: amal(at)guerrillamail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14246: Postgres crashing frequently
Date: 2016-07-13 08:29:46
Message-ID: 20160713082946.1409.98003@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14246
Logged by: Amal
Email address: amal(at)guerrillamail(dot)com
PostgreSQL version: 9.4.2
Operating system: Windows
Description:

Postgres is crashing frequently in windows server. pg_logs are as follows.
There is coming different reasons for each crashing. Could you please check
everything and give me some solutions for this problem.
______________________________________
LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.

LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


WARNING: worker took too long to start; canceled
LOG: server process (PID 123713) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 6012) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: pre-existing shared memory block is still in use
HINT: Check if there are any old server processes still running, and
terminate them.
LOG: database system was interrupted; last known up at 2016-05-23 12:34:12
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 0/ADE80E88
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: record with zero length at 0/B242D7B0
LOG: redo done at 0/B242D780
LOG: last completed transaction was at log time 2016-05-23
12:34:12.123-08
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
FATAL: terminating connection due to administrator command
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2016-05-23 17:23:54 PST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
LOG: server process (PID 83100) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 121204) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: pre-existing shared memory block is still in use
HINT: Check if there are any old server processes still running, and
terminate them.
LOG: database system was interrupted; last known up at 2016-05-28 18:32:18
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 4/79398188
LOG: record with zero length at 4/79EE4E18
LOG: redo done at 4/79EE4DE8
LOG: last completed transaction was at log time 2016-05-28
18:32:18.197-08
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
FATAL: could not reattach to shared memory (key=0000000000000130,
addr=0000000001010000): error code 1455
WARNING: worker took too long to start; canceled
LOG: server process (PID 191911) was terminated by exception 0xC000012D
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 144194) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: could not create shared memory segment: error code 1455
DETAIL: Failed system call was CreateFileMapping(size=120193040,
name=Global/PostgreSQL:E:/finance/pgsql/data).
LOG: database system was interrupted; last known up at 2016-05-28 20:02:00
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 4/7BAF3678
LOG: record with zero length at 4/7D6E8918
LOG: redo done at 4/7D6E88E8
LOG: last completed transaction was at log time 2016-05-28
20:02:00.102-08
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
LOG: server process (PID 38756) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 9919) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: pre-existing shared memory block is still in use
HINT: Check if there are any old server processes still running, and
terminate them.

LOG: database system was interrupted; last known up at 2016-05-29 07:15:32
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 5/366853A8
LOG: record with zero length at 5/37911400
LOG: redo done at 5/379113D0
LOG: last completed transaction was at log time 2016-05-29
07:15:32.188-08
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
FATAL: could not reattach to shared memory (key=0000000000000130,
addr=0000000001F10000): error code 1455
WARNING: worker took too long to start; canceled
WARNING: worker took too long to start; canceled
ERROR: could not write block 2751 in file "base/16384/153204": Not enough
space
CONTEXT: writing block 2751 of relation base/16384/153204
LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


LOG: incomplete startup packet
LOG: could not receive data from client: No connection could be made
because the target machine actively refused it.


LOG: received fast shutdown request
LOG: aborting any active transactions
LOG: database system was interrupted; last known up at 2016-05-30 12:52:12
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 5/43710D08
FATAL: the database system is starting up
LOG: unexpected pageaddr 5/3A5F6000 in log file 5, segment 71, offset
6250496
LOG: redo done at 5/475F2F00
LOG: last completed transaction was at log time 2016-05-30
12:52:12.019+02
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
LOG: server process (PID 40892) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: worker took too long to start; canceled
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 2616) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: pre-existing shared memory block is still in use
HINT: Check if there are any old server processes still running, and
terminate them.
LOG: database system was interrupted; last known up at 2016-06-01 06:12:22
PST
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: redo starts at 6/EFCADE8
LOG: record with zero length at 6/11817768
LOG: redo done at 6/11817738
LOG: last completed transaction was at log time 2016-06-01
06:12:22.161-08
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: database "finance" already exists
STATEMENT: CREATE DATABASE "finance"
LOG: unrecognized win32 error code: 1450
LOG: could not open temporary statistics file "pg_stat_tmp/pgstat.tmp":
Invalid argument
WARNING: worker took too long to start; canceled
WARNING: worker took too long to start; canceled
WARNING: worker took too long to start; canceled
WARNING: worker took too long to start; canceled
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
WARNING: autovacuum worker started without a worker entry
WARNING: autovacuum worker started without a worker entry
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
WARNING: worker took too long to start; canceled
WARNING: autovacuum worker started without a worker entry
LOG: server process (PID 141190) was terminated by exception 0xC0000142
HINT: See C include file "ntstatus.h" for a description of the hexadecimal
value.
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server
process
DETAIL: 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.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
LOG: archiver process (PID 190001) exited with exit code 1
LOG: all server processes terminated; reinitializing
FATAL: pre-existing shared memory block is still in use
HINT: Check if there are any old server processes still running, and
terminate them.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Waller 2016-07-13 10:42:09 Re: BUG #14237: Terrible performance after accidentally running 'drop index' for index still being created
Previous Message Andrew Gierth 2016-07-13 02:56:32 Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL