Postgres went unresponsive, now frozen. Most likely issue with attached volume.
twoabove
PROOP

10 months ago

Hey!

8 hours ago, I got a notification that my app is crashing - reason was that it couldn't connect to a Postgres instance (through the internal url).

I couldn't connect to it through the public url nor through the UI, and I didn't have any option to scale it down and up again, so I initiated a region transfer.

But the transfer failed, because the volume is stuck in Waiting to migrate... state, and now I'm in a soft lock where the app isn't working.

All apps are on Metal.

I need to get it running by Monday - this app supports a mixing and mastering competition, and is required for submissions. Any help is appreciated. Thanks!

Some more info:

The server crashes with connect ETIMEDOUT fd12:ed62:428:0:2000:1:923:71e1:5432 which makes sense.

Also, if that's an option, feel free to check the project out: project id is 9ebb3e9b-4888-4e42-b7a2-0cdf0d97ab5c

Solved

4 Replies

Railway
BOT

10 months ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!


Status changed to Awaiting User Response chandrika 10 months ago


chandrika
EMPLOYEE

10 months ago

Hi, I've fixed your migration so it's no longer stuck. Could you please revert the service back to the original region — we have a few volumes that cannot currently be moved across regions, but you should be able to access the volume now


twoabove
PROOP

10 months ago

Can confirm that things are working!


Status changed to Awaiting Railway Response Railway 10 months ago


Status changed to Solved twoabove 10 months ago


Railway
BOT

10 months ago

✅ The internal ticket Failed Volume Migration has been marked as completed.


Loading...