Cannot connect to database after migrating region
I migrated my redis instance from Oregon to Virgina and it has been unavailable since then
27 Replies
Project ID:
36b7ed87-018a-4331-b622-e608958a6ec436b7ed87-018a-4331-b622-e608958a6ec4
Tried redeploying it?
Is it on private network?
Yes - this happened last night
its on a public network
I understood there would be downtime, but how much? thankfully I did this on our QA environment
the db is on private network as stated by this page
so the second step in this page is telling the truth, since it can't connect to a private database?
but its also publically available no?
..i don't think so
I didn't have this issue before migrating it
that's not a public access point?
what does it says when u connect to it?
using the redis-cli
(or any other tool)
let me try it in cli
I/O errorin the box but can't talk to redis
yep, seems like we're gonna need to wait for a conductor to check this thread and flag the team
did u email railway yet?
just did - usually would get faster help here
I've seen a certain team member being tagged on multiple migration issue threads so i'm gonna do the same 😛
@thomas - weird region migration bug on redis
@Medim
While I love to help, only conductors can tag in team members per the Discord rules
thank you for the help 🙏 my services are currenly borked rn so any help would be greatly appreciated
thankfully this is only in QA 🙂
I personally can't figure out much more than yes this is strange and this needs attention from the team
Thread has been flagged to Railway team by @thomas.
thanks thomas, sorry for pinging you
And Medim, thank you for helping out here. No worries about pinging me. Everyone gets a warning.
We will be opening up applications? or something like that for the conductor role sometime this year.
It is a great idea to run things in QA first; this feels like a one-off. If you make a minimum viable project that reproduces this as not a one-off event, I can credit you some credits. I will let this wait for the support rotation to get to in general though.
To be clear even if this is a one off, we will help
haha ive been in the industry long enough to be burned by this so I always try to mitigate impact to my customers
credits would be greater - quicker service would be better 🙂
Welp that's some egg on my face. I am sorry for calling this a one off. This was a symtom of the ongoing #🚨｜incidents we are having with new database deploys
Hey we have the issue fixed. Can you confirm it's no longer affecting you @Shakibaba ?
this has been resolved, thank you!