25 days ago
i,
My PostgreSQL service has been in a crash loop since the May 19 platform disruption. I have already tried multiple manual redeploys from the dashboard but the error persists every time.
Error in logs: Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/6e97f8c7-862a-4d10-bb26-f163dc9a85bd/vol_hmbi37kgiy7a3fss
ERROR (catatonit:2): failed to exec pid1: No such file or directory
The volume mounts successfully each time, but the container cannot start.
Details:
Volume ID: vol_hmbi37kgiy7a3fss
Bind mount ID: 6e97f8c7-862a-4d10-bb26-f163dc9a85bd
Last normal Postgres activity in logs: 2026-05-19 16:07 UTC
I have production data on this volume that I cannot afford to lose
I have not deleted the service or the volume. Please help me either fix the container startup or migrate my data to a new Postgres instance.
Thank you
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
Thanks for reaching out. We sincerely apologize for the service disruption.
We're seeing recovery in our API, builds, and deployments. I've redeployed your service, and it seems to have come back online now. If your other services are having an issue, please try to give it a redeploy. We'll publish a public postmortem covering what happened when we're fully recovered.
For all customers, we’ll publish a detailed postmortem outlining what happened and the steps we’re taking to prevent similar incidents in the future. For Enterprise customers, service credits are covered under our SLA and will be reviewed as part of our post-incident process. For ongoing context while we work on a post-mortem, you can read our FAQ here
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Solved mykal • 25 days ago