PostgreSQL Volume Full - 60 Users Affected - Pro Plan - daring-elegance
ccfm-master
PROOP

2 months ago

URGENT: PostgreSQL volume is 100% full, database is completely down. Project: daring-elegance Pro plan subscriber. 60 active users are affected right now. Please increase PostgreSQL volume size to 5GB immediately.

Solved

5 Replies

chandrika
EMPLOYEE

2 months ago

Volume resizing is a self-service feature available on Pro plans. Could you click on the volume in your project canvas, then click "Live Resize" in the volume settings to increase the size? It'll be done live with no downtime (more details here: Using Volumes)


Status changed to Awaiting User Response Railway 2 months ago


chandrika
EMPLOYEE

2 months ago

Looking at the service you've linked, seems like you got this sorted already? Your Postgres is at 5GB


chandrika

Looking at the service you've linked, seems like you got this sorted already? Your Postgres is at 5GB

ccfm-master
PROOP

2 months ago

Thank you for your response. I already resized the volume to 5GB

using Live Resize, but PostgreSQL is still stuck in a crash loop

with the same error: "No space left on device"

It appears the volume resize did not propagate to the filesystem.

The database keeps crashing during WAL recovery at the same point.

I found a similar case in your community:

"Postgres Critical Failure: No space left on device after resizing"

That case was resolved by your platform team manually applying

the resize at the filesystem level.

Could you please escalate this to your platform team?

Volume: postgres-volume (daring-elegance project)

60 users are currently unable to use the service.


Status changed to Awaiting Railway Response Railway 2 months ago


ccfm-master
PROOP

2 months ago

Also, we expect to scale up to 200+ users in the near future. Would it be advisable to proactively resize the volume to 10GB or more now to prevent this issue from recurring?


sam-a
EMPLOYEE

2 months ago

Hi there! We took a look and can confirm that your volume resize to 5 GB was applied successfully. Your Postgres service also appears to be running normally now with its latest deployment in a successful state.

The crash loop you were seeing earlier was likely due to the database needing a clean restart after the resize completed. It looks like the redeploy resolved that.

Regarding scaling to 200+ users, proactively increasing the volume size is a good idea. You can resize at any time from the volume settings in your dashboard with no downtime. Just keep an eye on disk usage in the Metrics tab and resize before you approach the limit.


Status changed to Awaiting User Response Railway 2 months ago


Railway
BOT

2 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...