Your Postgres service is currently in a crashed state, and your companion service is unable to connect to it (showing repeated connection timeouts). This is very likely a result of the major service disruption earlier today, which affected the Image Registry among other components and has since been resolved. The "catatonit: failed to exec pid1" error typically indicates the container image was corrupted or incompletely pulled during the outage. Please try triggering a fresh redeploy of your Postgres service from the service settings (three-dot menu on the latest deployment, then "Redeploy") now that the incident is resolved - this should pull a clean image and restore the service.

"Redeploy did not fix it — same catatonit error again immediately after redeploy. Please investigate the Postgres service on EU West, the image seems corrupted again."

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.

Hello, my postgres service is still crashed and a redeploy presents the same error when mounting the volume:

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

Can you advise what to try?

Hey, sorry for the delay and the confusing canned responses above.

I just dug in here myself and I've redeployed your PostgreSQL service. It seems to have come back online. If your other services are having issues, please try to give them a redeploy and if you're still seeing problems reach out in this thread so we can assist.

We've also published a post-mortem if you'd like more information on the incident. In your case, the postgresql service just needed a redeploy to be routed to a healthy deployment

Again, we're deeply sorry that you were affected here.

Hi, I'm experiencing the same issue:

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

Tried multiple times to restart, with each crashing the same way.

Found a fix that works for me:

Database service > latest deployment > command palette Ctrl+K > Redeploy source image