My managed PostgreSQL service has been in a crash loop since ~05:01 UTC on May 20, 2026 —

coinciding with your infrastructure incident. The service mounts the persistent volume

successfully but fails immediately after with:

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

The database files on the volume appear intact (volume mounts without errors). The issue

seems to be with the container image, not the data.

Redeploying from the dashboard did not resolve the issue.

Service details

• Project ID: a523aec3-e9cc-4ad3-ba54-a9067b593716
• Environment: 6c2edae7-733f-4825-8e21-8f99201cafcd
• Service ID: e7b74fa9-97d0-4aae-96a6-741439de1da8
• Deployment ID: d4482052-b3a4-46d5-b59f-5c729c920762
• Replica ID: 9a24084b-cf2f-4243-83fd-f5b5592a89a1

Crash loop pattern (repeating since 2026-05-20T05:01 UTC)

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/

  9a24084b-cf2f-4243-83fd-f5b5592a89a1/vol_42ucwmpoobbd3xxa   [INFO]

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

The cycle repeats every ~10–15 seconds.

What I've tried

• Forced redeploy from the Deployments tab → same result

Request

1. Restore the managed PostgreSQL service to a working state without data loss
2. If not possible, provide access to the latest backup so I can restore to a new instance

Thank you.