Postgres service in infinite restart loop since 05/19 GCP outage - urgent
romeo1397
HOBBYOP

24 days ago

Image: ghcr.io/railwayapp-templates/postgres-ssl:18

This appears to be related to the 05/19 GCP outage — I see 5 similar threads

in the help section about Postgres containers stuck in catatonit pid1 errors.

Symptoms:

  • Postgres container infinite restart loop
  • Logs show repeating "ERROR (catatonit:2): failed to exec pid1: No such file or directory"
  • Repeated "Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/3c5af8d9-6d9d-49c9-b01a-d078c77bd68a/vol_hk9i13mane2q58jb"
  • Last successful PostgreSQL checkpoint: 2026-05-19 07:54:28 UTC

The container fails before PostgreSQL even starts — looks like the entrypoint

or postgres binary cannot be exec'd. Data volume should be persistent and intact.

No backups configured. Production application is blocked.

Need help:

  1. Recover the Postgres container so it can start reading the existing volume, OR
  2. Access the volume data to migrate to a fresh Postgres service

Project URL: https://railway.com/project/395239ce-7075-44c7-b024-4a5726fdfd67?environmentId=46fdc1da-6c30-40c2-b4ee-56f9ddcbe586

Solved

1 Replies

Railway
BOT

24 days ago

Your Postgres service has a stale container image, which is what causes the "catatonit pid1" error - the volume data is intact. To fix this, open the Postgres service, press Cmd/Ctrl+K to open the command palette, and select "Redeploy source image" to re-pull a fresh image. A normal redeploy from the 3-dot menu will not work because it reuses the cached image.


Status changed to Awaiting User Response Railway 24 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...