HELP! Subject: Services Crashed for 2 Days — Postgres Connection Failure

urquidi25

HOBBYOP

16 days ago

Description:

Both services in the production environment have been down for approximately 2 days:

Affected Services:

Garnix_Roolz (backend)

Postgres (database with persistent volume)

Error Details:

Backend crashes on startup with: Npgsql.NpgsqlException: Failed to connect to 10.135.201.169:5432

Error occurs during EF Core migrations in Program.cs:line 236

Connection times out during startup

Postgres service itself is crashed

Timeline:

Issue started ~2 days ago

Postgres crashed 9 minutes ago (most recent)

Garnix_Roolz crashed 43 minutes ago

Attempted restart of Postgres — did not resolve

Deployment ID: 8cf0c704-e575-4bec-9f8e-aafa1acb316b

Project: miraculous-presence (9a027b26-05c6-4e00-92b6-6a3dea6c949b)

Environment: production (3d484a83-3c93-4435-8cf3-c6becc33f76b)

$10 Bounty

2 Replies

Status changed to Open Railway • 16 days ago

0x5b62656e5d

MODERATOR

16 days ago

Try redeploying your Postgres service instead of restarting it.

testuser123

PRO

14 days ago

since Postgres itself is crashed, I would fix that before looking at the .NET app.

for the May 20 Postgres/catatonit style failures, restart usually does nothing. try Redeploy source image on the Postgres service from the command palette, not just restart from the three-dot menu.

also, if your backend runs EF migrations on startup, temporarily disable that until Postgres is healthy. otherwise the backend can keep crashing during boot and make it look like two separate problems.

Welcome!