Thread: Server process exited with exit code 4
I encountered a problem while using postgre(version 15.2) on windows 10. the following error messages are often printed in the logs, about once a day.
-----------------------------------
LOG: server process (PID 38540) exited with exit code 4.
DETAIL: Failed process was running: COMMIT
LOG: terminating any other active server processes
LOG: all server process terminated; reinitializing
LOG: database system was interrupted; last known up at 2023-10-17 00:47:17 HKT
LOG: connection received: host=127.0.0.1 port=58402
FATAL: the database system is in recovery mode
LOG: connection received: host=127.0.0.1 port=58407
FATAL: the database system is in recovery mode
...
LOG: connection received: host=127.0.0.1 port=58648
FATAL: the database system is in recovery mode
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 9/BDC88988
FATAL: the database system is in recovery mode
LOG: invalid record length at 9/BF49CF28: wanted 24, got 0
LOG: redo done at 9/BF49CF00 system usage: CPU: user: 0.10 s, system: 0.04 s, elapsed: 0.29 s
LOG: checkpoint starting: end-of-recovery immediate wait
LOG: checkpoint complete: wrote 1947 buffers (0.4%); 0 WAL files added; 0 removed, 2 recycled; write=0.057s, …
LOG: database system is ready to accept connections
----------------------------------
Sometimes it doesn't start with "server process (PID xxx) exited with exit code 4", but with "database system was interrupted".
These computers have relatively abundant resource, memory 192GB, hard disk 12T.
Installed plugin timescaledb (version 2.11.1) for compression and aggregation. it doesn't seem like a problem with timescaledb either, as this issue has only recently emerged.
Has anyone encountered similar problem or may know a solution?
Thanks.
-----------------------------------
LOG: server process (PID 38540) exited with exit code 4.
DETAIL: Failed process was running: COMMIT
LOG: terminating any other active server processes
LOG: all server process terminated; reinitializing
LOG: database system was interrupted; last known up at 2023-10-17 00:47:17 HKT
LOG: connection received: host=127.0.0.1 port=58402
FATAL: the database system is in recovery mode
LOG: connection received: host=127.0.0.1 port=58407
FATAL: the database system is in recovery mode
...
LOG: connection received: host=127.0.0.1 port=58648
FATAL: the database system is in recovery mode
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 9/BDC88988
FATAL: the database system is in recovery mode
LOG: invalid record length at 9/BF49CF28: wanted 24, got 0
LOG: redo done at 9/BF49CF00 system usage: CPU: user: 0.10 s, system: 0.04 s, elapsed: 0.29 s
LOG: checkpoint starting: end-of-recovery immediate wait
LOG: checkpoint complete: wrote 1947 buffers (0.4%); 0 WAL files added; 0 removed, 2 recycled; write=0.057s, …
LOG: database system is ready to accept connections
----------------------------------
Sometimes it doesn't start with "server process (PID xxx) exited with exit code 4", but with "database system was interrupted".
These computers have relatively abundant resource, memory 192GB, hard disk 12T.
Installed plugin timescaledb (version 2.11.1) for compression and aggregation. it doesn't seem like a problem with timescaledb either, as this issue has only recently emerged.
Has anyone encountered similar problem or may know a solution?
Thanks.
On 2023-10-30 14:02, yangsr3411 wrote: <snip> > Has anyone encountered similar problem or may know a solution? Just to rule out hardware problems, does the server hardware have some way of showing things like ECC memory errors and similar? Most official server hardware (HPE, Dell, etc) have utilities that can show a log of any recent weirdness that occurred at a hardware level. If yours can, take a look for things like ECC errors or any other strange stuff. :) Regards and best wishes, Justin Clift