a month ago
Hi team — hoping someone can help, I'm in a tough spot.
My Postgres service has been crash-looping for a few hours and it holds live data for my small business (scheduled posts for my coaching platform). Really hoping the data is still recoverable.
Account email: connormeyler@gmail.com
Project name: coaching dashboard
What I'm seeing in the logs:
-
Last successful Postgres checkpoint: 2026-05-19 11:02:08 UTC
-
Right after that, the container died and it's been crash-looping since with:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
-
The volume keeps mounting fine on every restart attempt — the line that repeats is:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/cf5624cd-fbc7-4193-9855-edfbe8673fce/vol_vggs290wfm21xu4a
-
I haven't touched the service since it crashed, didn't want to make things worse
I think an automated tool with access to my machine may have accidentally interfered with the service around that time.
If anyone has a moment to look, what I'd love is:
- For the volume to stay untouched (please don't recreate or wipe it)
- Help getting the data out — ideally attaching the volume to a working Postgres container so I can dump it
I'm on the Hobby tier and totally understand there's no SLA — just really grateful for any help. Thanks so much.
3 Replies
Status changed to Open Railway • about 1 month ago
a month ago
happening to me too!
a month ago
hey maybe this can help you
Deploy a new Postgres service (or a plain container like postgres:15) and in its settings, mount your existing volume (vol_vggs290wfm21xu4a) at /var/lib/postgresql/data instead of a new volume.
Once it starts cleanly, run pg_dump to export your data before doing anything else.
Then you can fix or redeploy your original service with confidence.