24 days ago
After the May 19 GCP platform outage, my Postgres service is stuck in a crash loop. Manual redeployments do not fix it, the service keeps crashing with the same error on every attempt.
Logs repeat endlessly:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/f26df044-a4c6-4a1f-9935-dfde3ba910bf/vol_leo568odofkgmjw5
ERROR (catatonit:2): failed to exec pid1: No such file or directory
The volume mounts successfully but the container fails to exec pid1. The Postgres container image appears to be in an inconsistent state on the node after the outage.
I have attempted multiple manual redeployments, none resolve the issue.
5 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
I have the same problem.
24 days ago
It's still happening for me as well - I saw another thread that said it was solved, but it's not for my deployments
24 days ago
A redeploy worked for me.
24 days ago
Okay, let me try that - I was trying the "Restart" which I thought was functionally the same. Looks like the redeploy worked. Appreciate it.
jnmclarty
A redeploy worked for me.
24 days ago
Yes! This worked for me too. As @bdronn mentioned, 'redeploying' and 'restarting' are two different things. Redeploying worked.
Status changed to Solved ville-prog • 24 days ago