Production Postgres failing to start + Limited Access on account
robertoalves2021
HOBBYOP

a month ago

Hi team,

My production database has been down for 14+ hours. The web service is online but the Postgres deployment is stuck in a restart loop with this error:

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

The image is ghcr.io/railwayapp-templates/postgres-ssl:18. Volume mounts successfully, but the container fails to exec. This started around 2026-05-19 22:15 UTC, coinciding with the Edge Network outage.

On top of that, my account is showing "Limited Access — Deploys have been paused temporarily", so I cannot redeploy, try a different image, or take any corrective action.

This is a production B2B SaaS with paying customers. Please:

Restore deploy access to my account

Help diagnose the Postgres image issue

Project: igort-ecommerce

Service: Postgres

Volume ID: vol_g2bctm5pvae24csl

Thanks,

Jailson

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


sam-a
EMPLOYEE

a month ago

Your account and subscription are in good standing. The "Limited Access" state you're seeing is because hobby plan deploys are temporarily paused while we recover from a platform-wide disruption that began on May 19. This is not specific to your account. You can follow recovery progress here: https://status.railway.com/incident/KVZ1Z8GY

The Postgres container crash (the catatonit/pid1 error) is consistent with this disruption affecting container infrastructure. Once hobby deploys are re-enabled, you'll be able to redeploy your Postgres service, which should resolve that error. Your volume data is preserved through this process. We're sorry for the extended impact on your production workload.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved sam-a about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...