server process exited with code 1 - Mailing list pgsql-general

From Eric Hill
Subject server process exited with code 1
Date
Msg-id BL0PR05MB50122BB2A0A2ACD45868C673F0459@BL0PR05MB5012.namprd05.prod.outlook.com
Whole thread Raw
Responses Re: server process exited with code 1  (Julien Rouhaud <rjuju123@gmail.com>)
Re: server process exited with code 1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

Hey,

 

We are experiencing a periodic PostgreSQL crash. It happens overnight when automated processes are updating content on our website.  My PostgreSQL version information is:

 

PostgreSQL 11.10, compiled by Visual C++ build 1914, 64-bit

 

It is running on Windows Server 2019 Standard.  We were having this same crash on PostgreSQL 9.6, also running on Windows Server, I believe 2012, before a recent upgrade.  Here is the relevant part of the log:

 

2021-04-23 03:20:57 EDT [5324]: LOG:  connection received: host=10.120.80.162 port=54017

2021-04-23 03:20:57 EDT [5324]: LOG:  connection authorized: user=dba_webjmp database=webjmp

2021-04-23 03:21:00 EDT [15776]: LOG:  server process (PID 14820) exited with exit code 1

2021-04-23 03:21:00 EDT [15776]: DETAIL:  Failed process was running: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;

2021-04-23 03:21:00 EDT [15776]: LOG:  terminating any other active server processes

2021-04-23 03:21:00 EDT [5324]: WARNING:  terminating connection because of crash of another server process

2021-04-23 03:21:00 EDT [5324]: 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.

2021-04-23 03:21:00 EDT [5324]: HINT:  In a moment you should be able to reconnect to the database and repeat your command.

 

I would really like for PostgreSQL to produce a crashdump of this crash but one is not produced.  I made a crashdumps folder in the data directory and gave it every permission I could think of, but no joy there.

 

We’ve looked at various aspects of the PostgreSQL instance and the  machine it is running on, and we don’t seem to be running into any resource constraints (connections, memory).  This is what I’m logging:

 

# pgBadger-approved log line prefix

log_line_prefix = '%t [%p]: '

 

# S1561728 - Log any query that takes > 250 milliseconds to return

log_min_duration_statement = 250ms

 

# Additional logging to troubleshoot crashes, also using pgBadger recommendations

log_checkpoints = on                    # Default is off

log_lock_waits = on                     # Default is off

log_connections = on                    # Default is off

log_disconnections = on                 # Default is off

log_temp_files = 0                      # log temporary files equal or larger

log_autovacuum_min_duration = 0         # log all autovacuums

log_error_verbosity = default           # default is the default

 

Any thoughts?  Any other information I could provide that would be helpful?

 

Thanks!

 

Eric

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: enable_seqscan to off -> initial cost 10000000000
Next
From: Julien Rouhaud
Date:
Subject: Re: server process exited with code 1