Open
Description
Healthchecks will run for days and then the database container will exit with this log message:
2025-06-17 19:22:20.625 UTC [44] FATAL: terminating connection due to administrator command
And once the DB goes down, healthchecks web app also goes down.
AFAIK there wasn't any corresponding user or automated action that would cause db to terminate.
Any steps to prevent this from happening?
Full log context
2025-06-17 18:37:51.909 UTC [27] LOG: checkpoint starting: time
2025-06-17 18:37:54.245 UTC [27] LOG: checkpoint complete: wrote 24 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.320 s, sync=0.005 s, total=2.337 s; sync files=24, longest=0.004 s, average=0.001 s; distance=52 kB, estimate=52 kB; lsn=0/1F526E8, redo lsn=0/1F526B0
2025-06-17 19:22:20.609 UTC [1] LOG: received fast shutdown request
2025-06-17 19:22:20.621 UTC [1] LOG: aborting any active transactions
2025-06-17 19:22:20.625 UTC [44] FATAL: terminating connection due to administrator command
2025-06-17 19:22:20.625 UTC [43] FATAL: terminating connection due to administrator command
2025-06-17 19:22:20.637 UTC [1] LOG: background worker "logical replication launcher" (PID 32) exited with exit code 1
2025-06-17 19:22:20.653 UTC [27] LOG: shutting down
2025-06-17 19:22:20.666 UTC [27] LOG: checkpoint starting: shutdown immediate
2025-06-17 19:22:20.818 UTC [27] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.046 s, sync=0.001 s, total=0.165 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=47 kB; lsn=0/1F52798, redo lsn=0/1F52798
2025-06-17 19:22:20.825 UTC [1] LOG: database system is shut down
Metadata
Metadata
Assignees
Labels
No labels