Skip to content
Postgres service stuck in crash loop after May 19 GCP outage
ville-prog
OP

6 months 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.

Solved

5 Replies

Status changed to Awaiting Railway Response Railway • 6 months ago


jnmclarty

6 months ago

I have the same problem.


bdronn

6 months 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


jnmclarty

6 months ago

A redeploy worked for me.


bdronn

6 months 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.

ville-prog
OP

6 months 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 • 6 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...