2 months ago
Postgres stuck in crash loop after volume resize. Dashboard shows 20GB
with only 4GB used but filesystem was never expanded. Same issue as
multiple resolved Central Station threads where Railway manually ran
the filesystem resize.
Error: FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
Volume ID: vol_5yyrdxpxdpuhc3qa
Project: thriving-communication (Pro plan)
Environment: production
Down since: ~12:30 PM today
Please help — production down 5 hours.
4 Replies
10+ hours down. No response. Pro plan customer. This is a known
Railway platform bug that has been fixed same-day for multiple
other customers this week. I need a Railway employee to manually
run resize2fs on volume vol_5yyrdxpxdpuhc3qa.
Production is completely down. Please escalate.
2 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • 2 months ago
2 months ago
Just a reminder that this is Discord and that comes with no guaranteed response from team member, or any support SLAs.
Going forward you might want to use our official forum for support.
Brody, thanks for your response and understood. However, I also have a Central Station thread open since yesterday with no response. Can you help?
2 months ago
Unfortunately, I cannot right now, I just felt that saying someone is better than leaving you hanging, as for your thread on the central station, it is still within the Pro plan's SLA of 3 days.
Going to close this thread out as a duplicate because that divides support's attention.
Status changed to Closed brody • 2 months ago