a month ago
Crashes seconds after each restart
Service: Postgres-AASD (ID: d96ca0ce)
Deployment: 61b96b4e
Occurred during the May 19/20 build incident
ERROR (catatonit:2): failed to exec pid1: No such file or directory
ERROR (catatonit:2): failed to exec pid1: No such file or directory
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/32f6f95f-1755-4d0f-bd3b-e12eda79a3dd/vol_n6ku5lat5tg6o6ay
3 Replies
a month ago
The "failed to exec pid1: No such file or directory" error on your Postgres-AASD service is a result of the May 19/20 platform incident, which caused corrupted image layers during builds. Triggering a new deployment (click the three dots on the crashed deployment and select Redeploy) will pull a fresh image and should resolve the crash. Your volume data is unaffected by redeployment.
Status changed to Awaiting User Response Railway • 28 days ago
Railway
The "failed to exec pid1: No such file or directory" error on your Postgres-AASD service is a result of the May 19/20 platform incident, which caused corrupted image layers during builds. Triggering a new deployment (click the three dots on the crashed deployment and select **Redeploy**) will pull a fresh image and should resolve the crash. Your volume data is unaffected by redeployment.
a month ago
Deploys have been paused temparily
Attachments
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
Deploys are temporarily paused platform-wide as part of the ongoing incident recovery. Once deploys are re-enabled, you'll be able to redeploy your Postgres service, which will pull a fresh image and resolve the crash. Your volume data will be preserved through the redeploy.
Status changed to Awaiting User Response Railway • 28 days ago
21 days 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 • 21 days ago