Off Topic > Drama
RTB Dedicated Hosting Service - Service Closing
Rub:
--- Quote from: comr4de on January 22, 2013, 07:08:07 PM ---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.
--- End quote ---
That'd be great. We use Barnabas' server as a live test server and we haven't had this issue, more information would help.
--- Quote from: jes00 on January 23, 2013, 07:51:11 AM ---
What?
Also: page 100 :)
EDIT: I rebooted the server and tried again and it worked.
--- End quote ---
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
Ephialtes:
--- Quote from: jes00 on January 23, 2013, 07:51:11 AM ---
What?
Also: page 100 :)
EDIT: I rebooted the server and tried again and it worked.
--- End quote ---
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.
Gloss²:
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.
Kalphiter:
Lag on NY02 is getting annoying.
Rub:
--- Quote from: Kalphiter on January 23, 2013, 08:59:58 PM ---Lag on NY02 is getting annoying.
--- End quote ---
--- Quote from: Rub on January 13, 2013, 06:27:44 AM ---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!
--- End quote ---
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".