Fatal Crash
calcrowcrab
HOBBYOP

2 months ago

My PostgreSQL service is stuck in a crash loop due to the FATAL: could not write to file pg_wal/xlogtemp error.33: No space left on device. I upgraded to the Hobby plan and increased the volume, but the filesystem wasn't resized. PostgreSQL completes WAL redo but can't write the xlogtemp file. Volume ID: vol_vi0ywzjemk14hjrd. Need the filesystem extended. Thank you so much for your help.

9 Replies

calcrowcrab
HOBBYOP

2 months ago

I just found the setting to resize, thank you!


calcrowcrab
HOBBYOP

2 months ago

I'm sorry, but it does look like the system crashed again and is giving me the same error.


2 months ago

Since you didn't link a service, please provide a link now.



2 months ago

Your volume resize to 5 GB didn't fully apply, which is why PostgreSQL was still running out of space. We've corrected this on our end 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.


calcrowcrab
HOBBYOP

2 months ago

Railway, you all have amazing customer service! Thank you so much!!


2 months ago

Thank you for the kind words!


calcrowcrab
HOBBYOP

2 months ago

I'm so glad I chose this service, you all have a good night.


2 months ago

You as well!


Welcome!

Sign in to your Railway account to join the conversation.

Loading...