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


Quote from: Kalphiter
I'm pretty sure this is the current and official RTB thread. I asked about being unbanned from RTBC, what's wrong with that? Please just don't delete things without explanation.

I'm more sure that its the RTB hosting thread as I'm not part of trunk RTB development at all. If you have requests email support@returntoblockland.com.
« Last Edit: January 21, 2013, 08:18:42 PM by Ephialtes »

I just had another idea.
You should integrate a not as feature filled but still console usable/chat listenable management client into RTB (the client add-on)

I just had another idea.
You should integrate a not as feature filled but still console usable/chat listenable management client into RTB (the client add-on)

I'd love to offer something like that for free but to be able to do it well it really does need an application on the same computer as the server for Blockland to relay that stuff and I'm not too keen on supporting standalone applications at the moment. Maybe in the future!

Just wondering, are you planning on adding the option to load things under your ownership or as public bricks with the panel?

Just wondering, are you planning on adding the option to load things under your ownership or as public bricks with the panel?
Suggested this a few pages ago.

Just a fyi. The console likes to lag up when trace is on. It starts to glitch up.

Just a fyi. The console likes to lag up when trace is on. It starts to glitch up.
Hard to get around this stuff; plenty of mods can make trace a headache to read. Maybe Badspot could implement an exemption system for trace, but good luck convincing him to.

Reactor's server has had some issues staying up and/or falling off of the server list. The longest it's stayed up for in the past week is one day. I'll get a console log for the next time this happens.


What?

Also: page 100 :)

EDIT: I rebooted the server and tried again and it worked.
« Last Edit: January 23, 2013, 07:55:54 AM by jes00 »

Reactor's server has had some issues staying up and/or falling off of the server list. The longest it's stayed up for in the past week is one day. I'll get a console log for the next time this happens.
That'd be great. We use Barnabas' server as a live test server and we haven't had this issue, more information would help.


What?

Also: page 100 :)

EDIT: I rebooted the server and tried again and it worked.
For future reference, a quick /reloadBricks will sort this, I believe it's a BL issue and there isn't much we can do about it. see below
« Last Edit: January 23, 2013, 10:54:39 AM by Rub »


What?

Also: page 100 :)

EDIT: I rebooted the server and tried again and it worked.

I *think* this happens when the bricks you're trying to load have no ownership assigned to them so it should be something I can fix to default to the user loading the bricks.

I don't think any of my console logs are saving. I just went to the latest one I have and it was *ithink* from yesterday, Because it had the chats from yesterday.

Lag on NY02 is getting annoying.

Lag on NY02 is getting annoying.
In future when reporting a problem please ensure you include the following information:
  • Node hostname or IP - it's important that you know which node you're reporting a problem for so we can match logs up and find the issue. If you report a problem without knowing what node you're on (the above example says lag on NY01 but reports the NY02 IP, what?), your report cannot be followed up.
  • Time and date including timezone - if we don't know when you're experiencing problems, we can't match logs up to work out and fix the problem. If there is a serious case of high latency and you don't think it's localised to you, it's important we find out times and routes so we can work with upstream providers to understand the issue.
  • Server host - lag can sometimes be caused by high CPU usage, this needs to be checked in logs too

If you don't include that information, your report is 100% useless, will be considered as spam and reported accordingly. I'm happy to hear reports of problems so we can fix them and improve service quality, but if we're not receiving data, nothing can be done.

Please don't ignore my request about information, it's not difficult to include it. Improving service quality is my primary concern and I don't really care who the reports come from, just that they include the required data for us to investigate. I'm currently adding more monitoring servers to our internal monitoring and will be looking to provide even more public reports in the future.

Thanks!

I went ahead and reported your post. All RTT data is looking normal, maybe if you weren't such a pathetic handicap and included some data I'd be able to look into the "problem".