24 days ago
I have a production DB and a test server that are continuing to crash a second after restarting them.
10 Replies
24 days ago
mee to
24 days ago
We experienced a platform-wide service disruption on May 20 between 02:25 UTC and 07:57 UTC that affected all regions. Looking at your account, your Postgres service in the Repsify Production environment has been in a crashed state since April 24 UTC, and your Repsify-Server in the Testing environment has been crashed since May 17 UTC, both predating this incident. Your other services (including Repsify-Server in Production) currently show a healthy status. Now that the incident is resolved, please try redeploying the two crashed services. If they continue to crash after redeploying, check the deploy logs in your dashboard for any error messages that appear on startup.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved Railway • 24 days ago
Railway
We experienced a [platform-wide service disruption](https://status.railway.com/incident/I23M92U0) on May 20 between 02:25 UTC and 07:57 UTC that affected all regions. Looking at your account, your Postgres service in the Repsify Production environment has been in a crashed state since April 24 UTC, and your Repsify-Server in the Testing environment has been crashed since May 17 UTC, both predating this incident. Your other services (including Repsify-Server in Production) currently show a healthy status. Now that the incident is resolved, please try redeploying the two crashed services. If they continue to crash after redeploying, check the deploy logs in your dashboard for any error messages that appear on startup.
24 days ago
Services continue to crash any time I restart them
Status changed to Awaiting Railway Response Railway • 24 days ago
Status changed to Open Railway • 24 days ago
24 days ago
Redeploys are now paused?
24 days ago
Unfortunately Hobby, Free, and Trial deployments had to be paused due to a huge backlog.
0x5b62656e5d
Unfortunately Hobby, Free, and Trial deployments had to be paused due to a huge backlog. https://status.railway.com/incident/KVZ1Z8GY
23 days ago
My production database continues to crash every after a redeployment
23 days ago
any additional info what's happening? logs?
23 days ago
ERROR (catatonit:2): failed to exec pid1: No such file or directory
looks like this is spamming occasionally within the deploy logs
23 days ago
This exact catatonit: failed to exec pid1 error has been reported in multiple Postgres/Railway services today after the May 19/20 platform incident (https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage)
Try to do a redeploy of a database service (deploys should be working now, they're resolved it). If redeploy succeeds, redeploy the dependent app service after the DB is healthy.