a month ago
Hi Railway support,
My pgVector-Railway service has been crashing in a loop for the past 12 hours and cannot restart. The error repeats indefinitely:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/50f2a031-c9e1-4180-b48a-485758dce028/vol_okv5ito7y9hip4p1
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Details:
Service: pgVector-Railway
Volume: vol_okv5ito7y9hip4p1
Last successful checkpoint: 2026-05-19 22:11 UTC
First crash: approximately 2026-05-19 22:15 UTC
Multiple manual restarts attempted — same error every time
The volume mounts successfully but the container cannot find its main executable (pid1). The PostgreSQL data appears intact based on the checkpoint logs before the crash.
The other services (Postgres, Redis, mAIstro web, worker, beat) are all online. Only pgVector-Railway is affected.
Can you check what happened to the container image for this service and restore it?
Thank you
4 Replies
Status changed to Awaiting Railway Response Railway • 27 days 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 • 27 days 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
Service still crashing after multiple redeploys.
Project ID: ea2fd509-503b-435f-844a-a6215a9b5694
Service ID: ab7a48a7-95b8-4df8-bea7-f7a31e6994f4
Environment ID: 98e8365c-a1be-4dd6-9238-3ce87087abf8
Volume ID: vol_okv5ito7y9hip4p1
Error: catatonit: failed to exec pid1: No such file or directory
Please move the volume to a healthy node. Do not reprovision — data must be preserved.
Status changed to Awaiting Railway Response Railway • 26 days 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.
24 days ago
hi, THIS IS THE SECOND MESSAGE IN ORDER TO GET YOUR RESPONSE.
MAY YOU GIVE ME AN ANSWER?
Service still crashing after multiple redeploys.
Project ID: ea2fd509-503b-435f-844a-a6215a9b5694
Service ID: ab7a48a7-95b8-4df8-bea7-f7a31e6994f4
Environment ID: 98e8365c-a1be-4dd6-9238-3ce87087abf8
Volume ID: vol_okv5ito7y9hip4p1
Error: catatonit: failed to exec pid1: No such file or directory
Please move the volume to a healthy node. Do not reprovision — data must be preserved.
Status changed to Awaiting Railway Response Railway • 24 days ago