3 months ago
Our managed Postgres service is still crashing after the recent Railway incident.
Current symptoms:
-
Postgres service crashes immediately after restart
-
Deploy logs repeatedly show:
"ERROR (catatonit:2): failed to exec pid1: No such file or directory"
-
Dependent app service fails to connect to Postgres with ECONNREFUSED on port 5432
-
Website returns 502
Project / service context:
- Project: selfless-spontaneity
- Environment: production
- Postgres service: 36438be2
- App service affected: website-hyungjun
- Custom domain: hyungjun.us
I believe this may still be related to the recent Railway/GCP incident:
https://status.railway.com/incident/I23M92U0
Could Railway confirm whether this Postgres service is still pending recovery or needs manual intervention?
1 Replies
3 months ago
Both your Postgres and website services in this project are currently in a crashed state. The "failed to exec pid1" error you're seeing is consistent with the ongoing service disruption, which affects Image Registry and all GCP regions. The latest incident update confirms that deploys are now possible but GCP-hosted workloads may still experience intermittent issues while recovery completes. Please try redeploying your Postgres service now that deploys are restored - if it still fails to start after a fresh deploy, let us know.
Status changed to Awaiting User Response Railway • 3 months ago
3 months 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 • 3 months ago