a month ago
URGENT - Postgres deployment crashed and won't restart
Status: Just upgraded to Pro plan. Postgres has been down for
~5 hours.
Symptoms:
Postgres shut down cleanly at 2026-05-19 22:22:42 UTC
("LOG: database system is shut down")
After shutdown, container fails to start with repeated
error: "ERROR (catatonit:2): failed to exec pid1:
No such file or directory"
Restart from UI shows "Completed" but no new logs appear
TablePlus connection fails with "server closed the
connection unexpectedly"
Deployment status shows "Online" target but reality is
"stopped running"
Volume appears intact (vol_6ih6yu64id6u3ifx).
This is a production database for a live trading platform.
Please help recover the service. Database has no recent
backups as I just upgraded to Pro today.
Thanks!
1 Replies
a month ago
Your Postgres service was affected by the May 19 service disruption, which impacted our Image Registry. The logs confirm Postgres shut down cleanly (completed checkpoint, no data corruption), and the volume is still mounting successfully on each attempt. However, the container image became unavailable during the outage, which is why every restart fails immediately. A "Restart" reuses the same cached image, so it will keep failing. To recover, go to the Deployments tab, click the three-dot menu on the crashed deployment, and select Redeploy - this will pull a fresh image. Your volume data should be preserved since Postgres completed a clean shutdown before the outage began.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago