11 days ago
2026-05-11 16:40:56.547 UTC [6] LOG: starting PostgreSQL 16.13 (Debian 16.13-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-05-11 16:40:56.547 UTC [6] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-05-11 16:40:56.547 UTC [6] LOG: listening on IPv6 address "::", port 5432
2026-05-11 16:40:56.554 UTC [6] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-11 16:40:56.564 UTC [29] LOG: database system was interrupted while in recovery at 2026-05-11 16:40:53 UTC
2026-05-11 16:40:56.564 UTC [29] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2026-05-11 16:40:57.039 UTC [29] LOG: database system was not properly shut down; automatic recovery in progress
2026-05-11 16:40:57.044 UTC [29] LOG: redo starts at 0/2EC1A788
2026-05-11 16:40:57.103 UTC [30] FATAL: the database system is not yet accepting connections
2026-05-11 16:40:57.103 UTC [30] DETAIL: Consistent recovery state has not been yet reached.
2026-05-11 16:40:58.361 UTC [29] LOG: redo done at 0/30FFFDE0 system usage: CPU: user: 0.03 s, system: 0.02 s, elapsed: 1.31 s
2026-05-11 16:40:58.381 UTC [29] FATAL: could not write to file "pg_wal/xlogtemp.29": No space left on device
2026-05-11 16:40:58.384 UTC [6] LOG: startup process (PID 29) exited with exit code 1
2026-05-11 16:40:58.384 UTC [6] LOG: terminating any other active server processes
2026-05-11 16:40:58.385 UTC [6] LOG: shutting down due to startup process failure
2026-05-11 16:40:58.392 UTC [6] LOG: database system is shut down
1 Replies
11 days ago
Your Postgres service crashed because the volume ran out of disk space, as indicated by the "No space left on device" error during WAL recovery. You can resolve this by performing a live resize on the volume attached to your Postgres service to increase its capacity, then redeploying the service.
Status changed to Awaiting User Response Railway • 11 days ago
4 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 days ago