a month ago
Project: pl-dashboard
Service: Postgres
Volume ID: vol_ch4euyxitfn0ajs8
Image: ghcr.io/railwayapp-templates/postgres-ssl:18
Region: Southeast Asia
Domain: postgres-production-9d34.up.railway.app
The Postgres container has been in a restart loop since 2026-05-20 04:20:13 UTC
with this error on every attempt:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
The volume mounts successfully on every attempt — only the container init binary
is broken. Last healthy checkpoint was 2026-05-18 10:28:58 UTC. Manual restarts
of both the active and a prior deployment fail identically.
Please either:
(a) repair/repush the postgres-ssl:18 image so the existing service can boot, or
(b) attach my volume vol_ch4euyxitfn0ajs8 to a new Postgres service so I can
recover the data without loss.Thank you.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey, sorry about the downtime. The catatonit pid1 error means the container image that was cached during the outage is broken. Your data on the volume is intact.
The fix: open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image". This re-pulls a fresh image while keeping your volume and data untouched. A normal redeploy from the 3-dot menu won't work because it reuses the cached broken image.
Let us know if that gets you back up.
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 • 29 days ago