7 days ago
Hi Railway,
Production Postgres billboard-bee-db in Billboard_Bee (production, US East) is stuck offline on “Resizing volume…”.
This looks like the same issue as Database unavailable – stuck on "Resizing volume..." (Davor / Christian): the UI hangs on resize, and a self-serve Live resize may not actually grow the volume.
Facts
Volume: sweet-2026-03-20 06:57 UTC (vol_x89krt3ip9fkjs2x)
Was 10 GB and 100% full
Postgres crash loop: FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
We started Live resize to 20 GB at ~06:14 UTC on 2026-08-14
25+ minutes later the canvas still shows “Resizing volume…” / Service offline
Metrics already show Max Size 20.00 GB, but the service never came back
Latest crashed deploy: 09f8179e
Please do not leave this on a 10 GB volume. If we redeploy now, Postgres will hit the same disk-full crash immediately.
Request: please grow the volume to 20 GB on our behalf (same as Christian did in that thread). Short downtime is fine. This is a production outage.
We have not restarted or redeployed during the resize.
Thanks.
1 Replies
7 days ago
The volume resize to 20 GB completed successfully and the volume is in a healthy state with roughly 10 GB used, so there is plenty of headroom. The Postgres service's deployment was torn down during the resize process and has not come back up, which is why the database is unreachable. Triggering a new deploy from the service's page in the dashboard will bring Postgres back online against the 20 GB volume. Your data is intact on the volume.
Status changed to Awaiting User Response Railway • 7 days ago
5 hours 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 5 hours ago