3 months ago
Project: diplomatic-warmth
Environment: production
Service: Postgres (with volume vol_rz9im37cn32639tg)
The Postgres service has been crashing repeatedly for ~1 hour. The process crashes before producing any output — we see
zero PostgreSQL logs, only the backend's P1001 connection errors. Console shows "No running instances."
External proxy (tramway.proxy.rlwy.net:57767) unreachable. Internal hostname (postgres.railway.internal:5432) also
unreachable from backend.
No backups configured (Hobby plan).
Suspected: volume disk full or OOM. Can you check the volume state and disk usage? We need to recover without data loss
if possible.
Pinned Solution
3 months ago
Try pressing Cmd/Ctrl + K and redeploy from source. If that doesn't work, I'd just try creating a new Postgres service, delete the old one, and drag the old volume onto the new service to swap the volumes.
3 Replies
3 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 3 months ago
0x5b62656e5d
Have you tried redeploying the service?
3 months ago
yes, several times
3 months ago
Try pressing Cmd/Ctrl + K and redeploy from source. If that doesn't work, I'd just try creating a new Postgres service, delete the old one, and drag the old volume onto the new service to swap the volumes.
Status changed to Solved 0x5b62656e5d • about 1 month ago