FATAL: could not write to file "pg_wal/xlogtemp.25": No space left on device
Anonymous
HOBBYOP

2 months ago

I got this error, so my postgres crashed. I resized the volume from 500MB to 5GB, but still the service keeps on crashing, and I also redeployed. Can someone help with this as I thought resizing should solve it.

Solved

2 Replies

Railway
BOT

2 months ago

The volume live resize feature is only available to Pro plan users and above, so on the Hobby plan, the resize would not have taken effect. Your PostgreSQL service is stuck in a crash loop because the volume remains full and cannot complete WAL recovery. You would need to upgrade to the Pro plan to use the live resize feature, or alternatively, create a new volume with more space and restore from a backup if one is available.


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Awaiting Railway Response Railway 2 months ago


2 months ago

Hey! The volume resize from 500 MB to 5 GB didn't fully apply on our end. We've corrected it and redeployed your service. You should now have the full 5 GB of disk space available.

We've also shipped a fix to prevent this from happening on future volume resizes.


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 about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...