5 months ago
My Postgress DB keeps loading the database connection infinitely
Attachments
7 Replies
5 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
5 months ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/4898fa77-1bff-47e4-acbf-5665f154c7a7/vol_6eyqjd8dfnuae7jt
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-09-10 18:10:10.389 UTC [2] LOG: starting PostgreSQL 16.10 (Debian 16.10-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2025-09-10 18:10:10.389 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-09-10 18:10:10.389 UTC [2] LOG: listening on IPv6 address "::", port 5432
2025-09-10 18:10:10.423 UTC [2] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-09-10 18:10:10.811 UTC [25] LOG: database system was interrupted; last known up at 2025-09-10 16:56:22 UTC
2025-09-10 18:10:21.171 UTC [25] LOG: syncing data directory (fsync), elapsed time: 10.34 s, current path: ./global/6115
2025-09-10 18:10:25.822 UTC [25] LOG: database system was not properly shut down; automatic recovery in progress
2025-09-10 18:10:25.981 UTC [25] LOG: redo starts at 0/4D072F0
2025-09-10 18:10:25.990 UTC [25] LOG: invalid record length at 0/4D0AE48: expected at least 24, got 0
2025-09-10 18:10:25.990 UTC [25] LOG: redo done at 0/4D0AE10 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2025-09-10 18:10:26.644 UTC [23] LOG: checkpoint starting: end-of-recovery immediate wait
2025-09-10 18:10:29.664 UTC [23] LOG: checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.545 s, sync=0.813 s, total=3.243 s; sync files=6, longest=0.522 s, average=0.136 s; distance=14 kB, estimate=14 kB; lsn=0/4D0AE48, redo lsn=0/4D0AE48
2025-09-10 18:10:30.143 UTC [2] LOG: database system is ready to accept connections
Stopping Container
5 months ago
Path: /healthz
Retry window: 5m0s
Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Attempt #2 failed with service unavailable. Continuing to retry for 4m38s
Attempt #3 failed with service unavailable. Continuing to retry for 4m26s
Attempt #4 failed with service unavailable. Continuing to retry for 4m12s
Attempt #5 failed with service unavailable. Continuing to retry for 4m2s
Attempt #6 failed with service unavailable. Continuing to retry for 3m36s
Attempt #7 failed with service unavailable. Continuing to retry for 2m56s
Attempt #12 failed with service unavailable. Continuing to retry for 17s
1/1 replicas never became healthy!
Healthcheck failed!
Attachments
5 months ago
did you try to redeploy/restart postgres?