Postgres service stopped during Railway Major Outage - existing volume attached
samo801
HOBBYOP

24 days ago

Hi Railway team,

My production Postgres service stopped during the current Railway Major Outage.

Project: gallant-magic

Environment: production

Service: Postgres

Region: US East (Virginia, USA)

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

Attached volume: postgres-volume

The attached postgres-volume still exists and is still attached. Please do not delete, detach, or replace it.

Current behavior:

  • Postgres deployment shows Completed.
  • Database tab says the deployment is offline / stopped running.
  • My web service is online but cannot load because it depends on this Postgres database.
  • Start Command is empty.
  • Required variables exist: DATABASE_URL, PGHOST, PGPORT, PGUSER, PGPASSWORD, PGDATABASE.

Deploy logs repeatedly showed:

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

I also saw repeated volume mounting log lines.

Because this happened during the active Railway Service Disruption / Major Outage, can you please confirm whether this is expected during recovery and help ensure the existing Postgres service starts again using the existing attached volume?

Please advise if I should wait for the incident recovery or if there is any safe action I should take. I do not want to risk the existing database volume.

Solved

1 Replies

Railway
BOT

24 days ago

Your Postgres service in US East is affected by the ongoing Railway Service Disruption. The catatonit / pid1 error you're seeing is an infrastructure-level symptom of this outage, not a problem with your service or volume. Services are recovering and we're automatically redeploying unhealthy workloads, but if your Postgres doesn't come back on its own, triggering a manual redeploy from the service's three-dot menu is safe - it will use your existing attached volume and will not delete or detach it.


Status changed to Awaiting User Response Railway 24 days ago


Status changed to Solved samo801 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...