17 days ago
Hello,
My Postgres database service has been crashing since May 20, 2026 at 04:48 UTC with the following error:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Details:
Service: Postgres
Deployment ID: ddb26bf8-184a-4aef-ac2b-6147fe2ac1ab
Project: heroic-vitality
Environment: production
Timeline:
Last successful operation: May 19, 2026 at 22:21 UTC (checkpoint completed successfully)
First error: May 20, 2026 at 04:48 UTC
No changes were made to the service or configuration between these times
Observations:
The volume mounts successfully before each crash attempt
The container fails to initialize immediately after mounting
Multiple restart attempts have not resolved the issue
The error suggests a container initialization failure, not a database corruption
The service has been continuously crashing for several hours. I have no backup of the data and need urgent assistance to restore the database.
Please advise on the cause and possible recovery options.
Thank you
1 Replies
17 days ago
Your Postgres service started crash-looping at 04:48 UTC on May 20, which falls within a major platform-wide service disruption that ran from 02:25 UTC to 07:57 UTC. The "failed to exec pid1" error is a container-level initialization failure, not database corruption, and your volume is mounting successfully on each attempt, which indicates the underlying data is intact. The crash loop is persisting because the existing deployment's container image was affected during the outage - a restart reuses the same broken image. To recover, please redeploy (not restart) the Postgres service from the three-dot menu on the crashed deployment, which will pull a fresh image while preserving your volume data. If a redeploy still produces the same error, try a rollback to the previous successful deployment from the same menu.
Status changed to Awaiting User Response Railway • 17 days ago
Status changed to Solved zhulinskiidanil • 17 days ago