a month ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/528387fb-e35a-41f7-b4b2-eedd046f7406/vol_aaa2x3q1ubyq389u
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
6 Replies
a month ago
I'm seeing the same issue.
Status changed to Awaiting Railway Response Railway • about 1 month ago
tmolinger
I'm seeing the same issue.
a month ago
Glad it's not just me. But, I mean, with that error message, it has to be some sort of disk failure, right?
milosharp
Glad it's not just me. But, I mean, with that error message, it has to be some sort of disk failure, right?
a month ago
My data volume looks fine. Seems like the Postgres binary/entrypoint script in Railway's container image is missing or broken or something like that
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
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.
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
FYI - redploy resolved this now. Make sure to click redeploy rather than just restart.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago