a month ago
Hi Railway team,
My Postgres database service has been in a crash loop for ~11 hours and won't recover. Every restart shows:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
It boots, mounts the volume, then exits with the above error before Postgres can start. Restarting the service repeats the same failure.
Project ID: 9f452b3d-b110-48b9-ad07-4dc711435223
Environment: 79d3f3ab-2862-4287-9900-7f17ed952e40
Service ID: 245dccb7-5609-4405-9394-d6357b73a374
Image: ghcr.io/railwayapp-templates/postgres-ssl:18
First crash: 2026-05-20T04:58:58Z
Deploys are also paused on the project ("Limited Access" panel)
This looks tied to the platform incident currently posted in the dashboard banner ("Builds are slow to progress…"). My data volume is intact — I just can't get the container's PID 1 to exec. My production app (FieldKin) is fully down until this is resolved.
Please could you:
Confirm whether this project is in scope of the current incident
Help unstick the Postgres container — either pin/rollback the image version or apply whatever fix you've shipped
Unpause deploys on the project
Thanks!
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The catatonit pid1 error is caused by a stale container image, and your volume data is intact. To fix it, open the Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image". A normal redeploy from the three-dot menu will not work because it reuses the cached image. The build incident that caused this has since been resolved, so the Limited Access restriction on your project should have lifted - if it is still showing, try refreshing your dashboard.
Status changed to Awaiting User Response Railway • about 1 month ago
brody
The catatonit pid1 error is caused by a stale container image, and your volume data is intact. To fix it, open the Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image". A normal redeploy from the three-dot menu will not work because it reuses the cached image. The build incident that caused this has since been resolved, so the Limited Access restriction on your project should have lifted - if it is still showing, try refreshing your dashboard.
a month ago
Thank you and this worked!!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago