20 days ago
After the May 19 platform outage, my Postgres service is stuck
in a crash loop. Logs show:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/4deddcbf-857a-4dfe-b9ed-9d3d18a52993/vol_ru1frljh2qfz99e6
ERROR (catatonit:2): failed to exec pid1: No such file or directory
(repeating endlessly)
The volume appears to mount successfully but the container
fails to exec pid1, suggesting the Postgres container image
may be in an inconsistent state on the node after the outage.
Restart attempts do not resolve the issue.
Project: saba-workflow
Service: Postgres
Environment: production
Region: US East
Project ID: 5d9a84d0-fc21-4a58-b9f8-de45526a7d99
My data on the volume appears intact - please do NOT take
any action that could affect the volume contents. I would
prefer the container image be refreshed/re-pulled without
touching the persistent volume.
Other services in the same project (web, saba-form) are
running correctly. Only Postgres is affected.
Thanks for the help.
1 Replies
20 days ago
Your Postgres crash loop with the "failed to exec pid1" error is a direct result of the recent platform disruption. Services have recovered, but some workloads still need a redeploy. We are automatically redeploying services we detect as unhealthy, but if yours hasn't recovered yet, please trigger a manual redeploy from the service's dashboard - this will re-pull the container image while leaving your volume data intact.
Status changed to Awaiting User Response Railway • 20 days ago
13 days 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 • 13 days ago