PostgreSQL crash loop after incident I23M92U0 – catatonit: failed to exec pid1 | Railway | Page 1

runic mist May 21, 2026, 8:42 AM

#

Two of my PostgreSQL services have been stuck in a crash loop since 2026-05-20, following incident I23M92U0. Both services show the same symptom: the volume mounts successfully, but the container immediately fails with:
ERROR (catatonit:2): failed to exec pid1: No such file or directory

Restart and redeploy have not resolved either service.

Affected services:
Project/Service ID 9a021f13-56ac-4444-8905-aa43351eafd7, volume vol_4pyafc2u4h32ti32
Project/Service ID e7e3f509-cab8-47ce-bad0-cef0a103eade, volume vol_nihlkv3wlodtxk6f

Since the volumes mount without errors, the data appears intact. Please reprovision the containers against the existing volumes without deleting them.

novel hatchBOT May 21, 2026, 8:42 AM

#

Linked Railway resource: 585917f7 / c9d0f675 / 808c9e17

hardy temple May 21, 2026, 2:33 PM

#

I'd try redeploying again.

fervent trellis May 21, 2026, 2:45 PM

#

(from the command pallet though)

#PostgreSQL crash loop after incident I23M92U0 – catatonit: failed to exec pid1