3 months ago
Starting Container
2026-02-25 00:16:46.802 UTC [7] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-02-25 00:16:46.909 UTC [30] LOG: database system was interrupted while in recovery at 2026-02-24 23:56:27 UTC
2026-02-25 00:16:46.909 UTC [30] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2026-02-25 00:16:47.419 UTC [30] LOG: database system was not properly shut down; automatic recovery in progress
2026-02-25 00:16:47.439 UTC [30] LOG: redo starts at 0/2154EE10
Certificate will not expire
PostgreSQL Database directory appears to contain a database; Skipping initialization
2026-02-25 00:16:46.669 UTC [7] LOG: starting PostgreSQL 16.11 (Debian 16.11-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-02-25 00:16:46.670 UTC [7] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-02-25 00:16:46.670 UTC [7] LOG: listening on IPv6 address "::", port 5432
2026-02-25 00:16:51.890 UTC [30] LOG: redo done at 0/26FFFFA0 system usage: CPU: user: 0.06 s, system: 0.15 s, elapsed: 4.45 s
2026-02-25 00:16:51.908 UTC [30] FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
2026-02-25 00:16:51.921 UTC [7] LOG: startup process (PID 30) exited with exit code 1
2026-02-25 00:16:51.921 UTC [7] LOG: terminating any other active server processes
2026-02-25 00:16:51.925 UTC [7] LOG: shutting down due to startup process failure
2026-02-25 00:16:51.940 UTC [7] LOG: database system is shut down
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/627ade4a-90d5-49a3-996b-64c974b98dca/vol_by5fz7ud1vwytedq
2 Replies
Status changed to Awaiting Railway Response brody • 3 months ago
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Closed brody • 3 months ago