Postgres service crashed after Railway incident - cannot restart
dstsebnem
HOBBYOP

17 days ago

Hello Railway Support,

My Postgres service has been crashing since the recent Railway incident and cannot restart. After clicking "Restart" it immediately shows as "Crashed" saying;

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/dcd70b3b-c099-4e63-b491-5d0b01ffb978/vol_8wmuzmf9nm9a6d1g

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

https://railway.com/project/d55fdca5-9884-4b45-a695-f11588d5dd7d/service/0595c747-ba36-4ba1-8b58-0d88e7a49360?environmentId=6a4d32ba-16fa-447c-9cf1-487639b194f1&id=cadf2a52-5407-41b6-bd1d-5e17afb70263#deploy

Can you please restore the Postgres service without resetting or deleting the volume?

Thank you!

Solved

1 Replies

Railway
BOT

17 days ago

Your volume data is intact. This error is caused by a stale container image, which can happen after an incident. To fix it, open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" - this re-pulls a fresh image and resolves the error. A normal redeploy from the three-dot menu won't work here since it doesn't re-pull the image.


Status changed to Awaiting User Response Railway 17 days ago


Status changed to Solved dstsebnem 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...