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

2 months ago

@Railway

My 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

Closed

6 Replies

karrassi-dev
HOBBYOP

2 months ago

@Railway Admin


2 months ago

What triggered this error? It started out of nowhere?


karrassi-dev
HOBBYOP

2 months ago

It started out of nowhere — no config changes, no deploys, no manual actions. The service just entered a crash loop on its own. The only thing I tried was 'Redeploy source image' via Cmd+K but the error persisted. The logs show ERROR (catatonit:2): failed to exec pid1: No such file or directory repeating continuously.


2 months ago

Do you have backups?


2 months ago

My suggestion is that you try to access it via SSH and pg_dump your data


2 months ago

You can set it's start command to sleep infinity to be able to SSH into it


Welcome!

Sign in to your Railway account to join the conversation.

Loading...