3 months ago
My managed Postgres service has been crash-looping for 3 days with catatonit: failed to exec pid1: No such file or directory. Volume: vol_ti87dkxzgoysf8wo. The postgres-volume is mounted but the container fails to start. I need help restoring the service without data loss.
3 Replies
3 months ago
This error is caused by a stale container image, and your volume data is intact. To fix it, open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to pull a fresh image. A normal redeploy from the three-dot menu won't work here since it reuses the cached image.
Status changed to Awaiting User Response Railway • 3 months ago
Railway
This error is caused by a stale container image, and your volume data is intact. To fix it, open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to pull a fresh image. A normal redeploy from the three-dot menu won't work here since it reuses the cached image.
3 months ago
Got the below error in logs.
May 24, 2026, 10:10 AM
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
Starting Container
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5ec16c32-b862-41f7-94e7-65de5fb41855/vol_ti87dkxzgoysf8wo
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Those logs confirm the stale image issue. A normal redeploy won't fix this since it reuses the cached image. You need to use the command palette: press Cmd+K (Mac) or Ctrl+K (Windows/Linux) while viewing the Postgres service, then select "Redeploy source image" to pull a fresh image. Your volume data is safe.
Status changed to Awaiting User Response Railway • 3 months ago
3 months 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 • 3 months ago