Production database down - Postgres container fails to start
alisbayri
HOBBYOP

25 days ago

Production database down - Postgres container fails to start

6 Replies

colpitts-dev
PRO

25 days ago

same, and I cannot even redeploy as deployments have been temporarily paused. Railway - please help


itpbprojects
HOBBY

25 days ago

Facing the same issue. Can't redeploy either.


marcolombardini
PRO

25 days ago

same here, - persistent infrastructure issue affecting your Postgres service across multiple deployments, a human agent will need to investigate the container creation failures on the platform side.


fungoshop
HOBBY

25 days ago

Same issue here. Project ID: 0597ee55-88e4-4c48-90f1-532f934bd010. Postgres in crash loop with catatonit:2 failed to exec pid1: No such file or directory. Already tried Restart, no luck. Need urgent help.


fungoshop
HOBBY

24 days ago

Update: Railway platform is fully operational again (status page green),

but my Postgres service sistema_logistica is STILL in crash loop with:

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

App container selfless-integrity is online but cannot connect to DB.

Volume postgres-volume appears intact. This needs manual intervention

on the container creation side, as @marcolombardini mentioned earlier.

Project ID: [pega no Railway, canto inferior esquerdo]

Service: sistema_logistica (Postgres)

Region: [a região que aparece]

Can someone from Railway team please look at this?


colpitts-dev
PRO

24 days ago

FWIW - i had to nuke the existing Postgres database, and deploy a fresh db to get out of this - Luckily i had my PRODUCTION data backed up.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...