Postgres stuck in crash loop — failed to exec pid1
karrassi-dev
HOBBYOP

25 days ago

y PostgreSQL service is stuck in a crash loop and cannot start.

▎ Volume ID: vol_jc0dbfi04g2v6hye

▎ Logs show this repeating continuously:

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

▎ I already tried "Redeploy source image" via Cmd+K — the error persists.

▎ The volume contains live production data. Please migrate the service to a healthy node and preserve the volume.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 25 days ago


The Postgres service that was stuck in the crash loop has been removed, and a new Postgres deployment is now running successfully in this environment. Please confirm whether that replacement was intentional on your side, and if you still need data recovered from the original volume, let us know before making any further changes.


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