a month ago
Project: creative-stillness
Service: Postgres
Volume: postgres-volume (mount: /var/lib/postgresql/data) Volume was at 100% capacity (500MB). Initiated live resize to 5GB over 35 minutes ago. Status still shows "Resizing volume..." and Postgres crashes on every restart with "No space left on device" during WAL recovery. The n8n application service depends on this Postgres and is also down. Need the resize to complete or manual intervention. This is blocking our production system.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
UPDATE: Volume shows 5GB in UI but Postgres still crashes with "No space left on device" on pg_wal/xlogtemp.
The live resize from 500MB to 5GB appears to not have applied to the actual filesystem despite showing as complete in the UI. Postgres cannot complete WAL recovery.
Deploy logs show: - "database system was interrupted while in recovery" - "FATAL: could not write to file pg_wal/xlogtemp.29: No space left on device"
This has been going on for over 1 hour.
Need manual intervention to either: 1. Force-apply the volume resize to the actual filesystem
2. Or clear the pg_wal directory to allow Postgres to start Project: creative-stillness Service: Postgres Volume: postgres-volume
a month ago
Hey, we've fixed this. The volume resize to 5GB didn't fully apply to the disk — it was stuck at 500MB. We've expanded the filesystem and redeployed your Postgres service. It should be coming back up now with the full 5GB available and your data intact. Your n8n service should reconnect automatically once Postgres is up.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • about 1 month ago