Production Postgres crash-loop, volume reports 0MB, need emergency snapshot restore
mattdentist
PROOP

2 months ago

Project ID: 594d190c-acb7-4736-99f7-77736db70b71

Environment: production

Service: Postgres (ID: 4d65c128-7c4b-4b88-8879-66f157810dbe)

Volume: postgres-volume (ID: 801308d3-b052-4731-baef-5e37b78099be)

Request: Restore volume snapshot from before 2026-04-27 12:53 UTC

Urgency: Production database down, crash loop, no user backups

Solved

11 Replies

2 months ago

Can you share the exact crash logs?

Were you able to expand the DB volume?


mattdentist
PROOP

2 months ago

(no markdown available for this content)

Attachments


2 months ago

I need your DB crash logs, this is from your API service


mattdentist
PROOP

2 months ago

Sorry I can't seem to find them. The agent is saying this: The Postgres container is crashing before it can emit any startup output. The volume mounts, then the container exits silently.


2 months ago

You are running railway up against your database.


mattdentist
PROOP

2 months ago

Wow...yeah. Thank you. Will the existing pgdata on the volume mount correctly, or do I need to do anything special first? First time I've made this mistake.


2 months ago

Unless the code you uploaded specifically decided to delete /var/lib/postgresql/data, you are fine.

I have already redeployed the original image for Postgres and the database is back online, so please run railway service to switch the upload target to your dashboard service.


mattdentist
PROOP

2 months ago

Thanks a ton. You're a lifesaver!


2 months ago

No problem


2 months ago

Nothing Medim couldn't have instructed you to do, but they were working with limited information.


mattdentist
PROOP

2 months ago

Appreciate both of y'all for jumping in so quick!


Status changed to Solved brody 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...