2 days ago
My Postgres database service (project: talented-rebirth / renacimiento talentoso, service: Postgres) is stuck in a crash loop with the error ERROR (catatonit:2): failed to exec pid1: No such file or directory, repeating on every restart attempt. I've tried Restart, Redeploy, and "Redeploy source image" from the command palette — same error every time. There are no backups available for this volume. My application (delta-backend) was connecting to this database successfully just before this started. Can you please help restore the container / volume without data loss?
3 Replies
2 days ago
The catatonit: failed to exec pid1 error is caused by a stale container image, and "Redeploy source image" from the command palette (Cmd/Ctrl+K) is the correct fix. Your Postgres service's latest deployment is currently showing as successful and your volume data is intact (the volume is attached and holding data), so a recent redeploy source image attempt may have resolved it. If the error is still occurring, please try "Redeploy source image" once more from the command palette, as a normal redeploy or restart does not re-pull the image and will not fix this.
Status changed to Awaiting User Response Railway • 1 day ago
a day ago
Thanks for the suggestion, but I already tried "Redeploy source image" from the command palette multiple times (most recent deployment IDs: da845cb9, dd51d732), and the error persists identically every time:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
It keeps looping — mounting the volume, then immediately failing to exec pid1, over and over. A normal restart doesn't help either. Could someone take a closer look at the container image for this specific Postgres service? My data should still be on the volume (postgres-volume), I just need the container to actually boot.
Status changed to Awaiting Railway Response Railway • 1 day ago
a day ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 1 day ago
a day ago
Can you confirm that you opened the Command Palette (Ctrl+K) correctly? The error should be gone since Redeploy source image will re-pull the fresh image
If you sure you did it correctly, Try spin up a new Postgres service
Attachments