a month ago
After a Railway platform disruption earlier today, my Postgres database service stopped working. The container keeps failing with this error:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
The volume mounts successfully, but the container can't initialize. The error repeats continuously.
What I've tried:
Attempted to redeploy the service, but got API errors
The Deploy button is missing from the service UI
Restart attempts don't resolve itWhat I need:
The Postgres container to start successfully
Data on the persistent volume to be preserved (it's still mounted)
The service to be accessible againDetails:
This happened immediately after the platform disruption
The volume is mounting correctly, so the data is intact
Other services in the project are still running fine
The issue appears to be with the container image or init systemHas anyone else experienced this after the disruption? Any workarounds or solutions?
3 Replies
a month ago
Your Postgres service is currently in a crashed state, and this is consistent with the ongoing major service disruption affecting deployments, build machines, and image registries across all regions. The "failed to exec pid1" error and missing Deploy button are symptoms we're seeing broadly during this incident. Deploys are beginning to come back online, so we recommend attempting a redeploy of your Postgres service once things stabilize further. Your volume data will be preserved through redeployments.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your Postgres service is currently in a crashed state, and this is consistent with the [ongoing major service disruption](https://status.railway.com/incident/I23M92U0) affecting deployments, build machines, and image registries across all regions. The "failed to exec pid1" error and missing Deploy button are symptoms we're seeing broadly during this incident. Deploys are beginning to come back online, so we recommend attempting a redeploy of your Postgres service once things stabilize further. Your volume data will be preserved through redeployments.
a month ago
Still not working for me. failing with ERROR (catatonit:2): failed to exec pid1: No such file or directory
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We checked your Postgres service and confirmed it is still crash-looping with the pid1 error from a deployment at 05:13 UTC. The container image was likely corrupted during the earlier service disruption, which has since been resolved. A fresh redeploy should pull a clean image and fix it, but there is currently a separate build backlog that has temporarily paused new builds on hobby plans while we clear the queue. Once builds resume for your plan, triggering a redeploy from the service's three-dot menu should resolve this. Your volume data is preserved across redeployments.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 1 month ago