a month ago
My Postgres service (vol_pq66dhmktr2b4ibw) is crash-looping and cannot start. The database was not properly shut down and during WAL recovery it runs out of disk space:
FATAL: could not write to file "pg_wal/xlogtemp.33": No space left on device
WAL replay completes successfully (redo done at 1/2AFFFE88) but the final checkpoint write fails due to no free space.
I've already resized the volume in the dashboard and redeployed, but the container still reports no space. The service is stuck in a restart loop.
Project: PingTrade
Service: Postgres
Volume ID:vol_pq66dhmktr2b4ibw
Environment: production
What I need:
- Clear old WAL segments or expand the filesystem so Postgres can complete recovery
- OR mount the volume with the new size (current resize doesn't seem to have taken effect)
I cannot shell into the Postgres container remotely, so I can't fix this myself.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your volume resize didn't fully apply to the disk, which is why Postgres couldn't complete its recovery. We've corrected this on our end and redeployed your Postgres service. You should now have the full 5 GB of disk space available, and Postgres should be able to finish its WAL recovery and start normally.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved barel31 • about 1 month ago