Author Topic: RTB Dedicated Hosting Service - Service Closing  (Read 364325 times)

so did mitigation like already happen for the rest of the servers or is that still on hold?

We'll be starting that in the next few hours. We've got a high level of confidence in our new ny05 node at this point having run a few test servers on it so we think it'll be ready to accept migrations at this point. We'll be doing a further communication on that soon.

We're seeing really fantastic performance on our next-gen nodes so it's exciting that everyone will be able to benefit from them over the coming days.
« Last Edit: August 05, 2013, 11:34:21 PM by Ephialtes »

my newly renewed server is getting massive lagspikes, anyone know the cause of this?

Nobody knows the cause of it unless you submit a support ticket when it's happening. How can we diagnose issues if we don't know the time it happened, or your server ID?

We've now opened up migrations to all remaining servers on NY01 and NY03, please jump in the queue at your earliest convenience. We'll be adding all unmigrated servers to the queue at this time tomorrow.


After migrating, it seems my server is stuck when I try to start it up.
The last thing said in the console is "Engine initialized..."
I don't know if this is my fault or just the migration's. (my blid is 2983)

After migrating, it seems my server is stuck when I try to start it up.
The last thing said in the console is "Engine initialized..."
I don't know if this is my fault or just the migration's. (my blid is 2983)

As mentioned in the migration message, you need to re-enter your key after the migration either via the Change Key page or via the console itself if you know how to do that. You'll see in your activity stream (and also at the top of the page when you start the server) that the server is requesting you to re-enter your authentication key too.

For future issues it'd be far better to use the inbuilt support system - not only does it notify our cellphones about a new ticket but it'll email you with a notification when we reply to it too. It's a much more effective way to sort something as quick as possible.
« Last Edit: August 06, 2013, 04:49:41 PM by Ephialtes »

Thank you! I must have not noticed it when migrating.

The system allowed me to choose when I wanted to migrate and told me how far it was during the entire process.

It was fast and easy and my server is working perfectly.

Happy customer, /support.

So who won the RTB idea competition?

Thanks to everyone who's migrated their server so far for being so proactive. We have about 28 migrations left to perform now.

If these servers aren't migrated by the owners within the next 24 hours we will unfortunately have to force the servers to shut down and migrate them on our own schedule. We'll be retiring our legacy nodes in just over 24 hours so it's vital migrations are all completed before this occurs for obvious reasons.

I'm excited for the migration.  :)
Is RTB's connection failures related to this or the rumored* DDoS attacks?

*Not confirmed.

Also, nice 11111st post.

RTB and RTB Hosting are two separate things. There have been no connection issues for RTB Hosting and this is clearly not the thread for RTB questions.

My server is stuck on "Stuck", I entered my authorization key then tried to force shut down and now I can't do anything.

My server is stuck on "Stuck", I entered my authorization key then tried to force shut down and now I can't do anything.

Please raise a ticket. I would have seen this 15 minutes ago if you had and I'd also be able to look into it without having to ask which of your two servers you're talking about.