a month ago
The general incident was marked as resolved but my volume is still not mounting.
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/565b53bb-754f-4af8-b22a-d982fb75f57a/vol_masstw31fc8n22kx
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Manual restart does not help — same error repeats. The volume appears to be stuck or corrupted on your infrastructure side. Please check if the volume can be recovered or if a snapshot restore is possible.
This is a production database. Please prioritize.
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
Status changed to Awaiting User Response Railway • about 1 month ago
sam-a
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. [We've published a post-mortem if you'd like more information on the incident](https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage). It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you. It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process. You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c Feel free to respond if your question has not been addressed.
a month ago
hello Sam,
The issue is still ongoing, and as we can see from the link you provided, it doesn’t appear to have been resolved yet. Do you have an estimated timeline?
Thank you.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
If my database disappeared during all these problems, what should I do? How can I recover the data?
yugoru
If my database disappeared during all these problems, what should I do? How can I recover the data?
a month ago
i have redeployed my postgresql & backend services and it worked! i have no problem for now.
Status changed to Solved nuvlt • about 1 month ago