Production down — Postgres catatonit pid1 error
cfowiz
HOBBYOP

a month ago

Project: oktapod

Service: Postgres

Deployment: 16f4d738

Postgres has been crash-looping since Mar 19, 2026 22:36 EDT with:

ERROR (catatonit:2): failed to exec pid1: No such file or directory

The volume mounts successfully but the container exits before reaching Postgres entrypoint. Manually restarted just now (May 21, 9:11 AM EDT) — failed within 13 seconds with the identical error.

This appears to be a platform-level issue with catatonit rather than a Postgres or volume problem. Our entire team is blocked from production. Please advise on ETA or a workaround.

Closed

2 Replies

Railway
BOT

a month ago

This error is caused by a stale container image and a normal restart or redeploy won't fix it because it reuses the cached image. To resolve it, open the Postgres service, press Cmd/Ctrl+K to open the command palette, and select "Redeploy source image" - this re-pulls a fresh image and resolves the catatonit error. Your volume data is intact.


Status changed to Awaiting User Response Railway about 1 month ago


Railway

This error is caused by a stale container image and a normal restart or redeploy won't fix it because it reuses the cached image. To resolve it, open the Postgres service, press Cmd/Ctrl+K to open the command palette, and select "Redeploy source image" - this re-pulls a fresh image and resolves the catatonit error. Your volume data is intact.

javamuradov
PRO

a month ago

Had the same issue as described in this thread. Redeploying source image resolved it. Thanks!


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Closed Railway about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...