Postgres stuck in crash loop after May 19 GCP outage - failed to exec pid1
marica57
HOBBYOP

16 days ago

Same issue as the solved thread. My Postgres service has been crashlooping since May 19 GCP outage.

Error: ERROR (catatonit:2): failed to exec pid1: No such file or directory

Volume is mounting but PostgreSQL binary is missing. Manual redeploy doesn't fix it. Need Railway team to manually redeploy the service from their side like they did for others.

Volume ID: vol_rmr8a76p7if18xmz

Project: map-app

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 16 days ago


chandrika
EMPLOYEE

16 days ago

Hey, this is the same outage-related image issue. A normal redeploy reuses the cached broken image, which is why it didn't help.

The fix: open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image". This forces a fresh image pull. Your volume and data stay intact.

Let us know if that works.


Status changed to Awaiting User Response Railway 16 days ago


Railway
BOT

8 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 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...