a month ago
My PostgreSQL service is stuck in a crash loop and cannot start.
Project: dukaos
Service: Postgres
Service ID: 19108238-162f-48a6-ac9d-e490289601aa
Volume ID: vol_atgie7ctzjx55kum
Environment: production
Logs show this repeating continuously:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/c56963cd-6e9e-4942-9624-91dc5fc70770/vol_atgie7ctzjx55kum
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Restarting via CLI (railway service restart) has no effect — the error
persists immediately after every restart attempt.
The service shows SUCCESS in the dashboard but PostgreSQL is not actually
running — all database connections from the backend time out with P1001.
This appears to be a host-level container issue (the PostgreSQL binary
cannot be found inside the container). Please migrate the service to a
healthy node or repair the container image.
The volume contains live production data so please preserve it.
1 Replies
Status changed to Awaiting Railway Response Railway • 29 days ago
a month ago
This error is caused by a stale container image, and your volume data is safe. To fix it, open the Postgres service in the dashboard, 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 3-dot menu will not work since it reuses the cached image.
Status changed to Awaiting User Response Railway • 29 days ago
Status changed to Solved Railway • 29 days ago