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

1. Purchase all RTB Servers
2. Resell
3. ???
4. Profit!

1. Purchase all RTB Servers
2. Resell
3. ???
4. Profit!
I don't think this is a joke so I will tell you that anyone with ready access to the source material gets the best deal.

If I order now will my money just be pulled into a void of darkness or is it still purchasable?

EDIT: It says unavailable, but that's what it said last night when you guys were still taking orders, so idk.

I don't think this is a joke so I will tell you that anyone with ready access to the source material gets the best deal.
It's a joke...

Reactor's went down again, however there was no console log pertaining to the time of the crash.

Reactor's went down again, however there was no console log pertaining to the time of the crash.

Reactor's server doesn't seem to crash it just gets stuck and hangs with full CPU use so it'll only upload a console log once it's been shut down. There's an issue at the moment whereby a force shutdown won't produce a console.log to be downloaded which I'll look into.

I've had a bit of a look into some of Reactor's crashes and it's consistently happening after player persistence saves. I've brought up the file object crashing issue with Badspot who's been looking at it but we've not come up with a replicable scenario yet. I'd suggest disabling the player persistence add-on too since that's exacerbating whatever issue exists with file objects.

There's going to be a maintenance window of 2 hours for the webserver on February 3rd, from 10:00 PM EST to 12:00 AM EST during which time you won't be able to manage your server. All servers will remain up during this time.

There's going to be a maintenance window of 2 hours for the webserver on February 3rd, from 10:00 PM EST to 12:00 AM EST during which time you won't be able to manage your server. All servers will remain up during this time.
mk

I've had a bit of a look into some of Reactor's crashes and it's consistently happening after player persistence saves. I've brought up the file object crashing issue with Badspot who's been looking at it but we've not come up with a replicable scenario yet. I'd suggest disabling the player persistence add-on too since that's exacerbating whatever issue exists with file objects.
He could package the function that saves persistence files to toggle trace when it's called then turn it back off afterwards, maybe even do a console dump of the client before-hand as well. Would help indicate what's going on script-wise or at the very least provide more data for replication.

He could package the function that saves persistence files to toggle trace when it's called then turn it back off afterwards, maybe even do a console dump of the client before-hand as well. Would help indicate what's going on script-wise or at the very least provide more data for replication.
Clever idea. I never thought of doing that for a crashing issue.

He could package the function that saves persistence files to toggle trace when it's called then turn it back off afterwards, maybe even do a console dump of the client before-hand as well. Would help indicate what's going on script-wise or at the very least provide more data for replication.

It's not something that can easily be replicated, it's more of a subtle engine issue.

This is the second time RTB disabled all the add-ons I just enabled! >:(

Why RTB, WHyyyyyy

EDIT: I can't enable any add-ons :0 I'll submit a ticket for your tickety convenience.

EDIT2: Apparently dots in filenames is a very bad thing...
« Last Edit: February 01, 2013, 01:46:55 PM by Reinforcements »

my buddy just paid for a 3 month for us.

we trying to figure out how to use lol

Renewing resets the time to 31 days (for one month) and not whatever was left + the amount I renewed for?

Renewing resets the time to 31 days (for one month) and not whatever was left + the amount I renewed for?

You had 3 days left over on your contract and you renewed for a month in February which is 28 days, so you'd have 31 remaining which seems to be the case.