RTB Dedicated Hosting Service - Service Closing

[Ephialtes]

The server has crashed 5 times or so in the last hour.

Unfortunately server crashes aren't something that can really be caused by the service. We've got at least 25 other servers on your node which aren't crashing at all which means you'll need to look at your console.log and disable your add-ons to determine what's causing the crashes.

At the end of the day we're just providing a computer for you to run your server on - if that server is crashing it's something to do with whatever you're doing with it or running on it.

[Ad Bot]

[Rusty]

Turns out it was some poorly made event, nevermind.

[Wink]

How do I up the schedule limit and vehicle limit? I tried to do it with the FTP but it didn't change for some reason.

[Greek2me]

Turns out it was some poorly made event, nevermind.

Please report it or something.

[BlockoBlocko]

How do I up the schedule limit and vehicle limit? I tried to do it with the FTP but it didn't change for some reason.

1. Open the admin menu.
2. Click the game mode button.
3. Change the mode to custom and then hit advanced on the left.
4. Change any settings you want to change there, including vehicle limits.
5. Apply the settings and wait for the server to restart.

[Ephialtes]

How do I up the schedule limit and vehicle limit? I tried to do it with the FTP but it didn't change for some reason.

I can actually link you to our WIP FAQ page: https://hosting.returntoblockland.com/hosting/faq#changing-quotas

It's not entirely complete yet hence why it's not on any menu or linked from anywhere but it should still be useful in this instance.

[Ephialtes]

Small Update

Hi guys, so today I've been gently pushing out a new update for various parts of the service which is mostly bug fixes. Here's the list of items being deployed:

• Chat logs now function correctly.
• Server uptimes should no longer get stuck at 1 second.
• If your console output exceeds a certain rate you'll be warned and it may be disabled, read more here.
• Better detection and reboot behavior when a server crashes with 100% cpu use.
• Cases where the player list on the server chat page would be empty are now fixed.
• Character encoding issues preventing players with utf8 characters in their names from appearing on the activity stream are resolved.
• Console logs are now properly archived when the server is forced to shut down.
• Monitoring added on nodes to catch instances of wrapper jailbreaks.
• Changes made to add resilience to resource reporting on nodes.
• New FAQ page here.

One word on the console output disabling - I feel like the rates have been set fairly liberally (it should be around 3 lines per second for a warning, 6 lines per second consistently for output to be disabled) however if you're having to deal with this a lot please discuss in this thread and we'll work out a better limit.

Please note in order to fully update you only need to stop and start your server (a reboot isn't enough). You can of course update at your own convenience - all functionality should continue to work until you choose to update.

As ever, if there are any issues then please raise a ticket and we'll sort that out.

[Kimono]

how long does your server stay existant after it expires?

mine expired yesterday and i couldnt renew it as the person that owns the server was at working

how long does it last?

[Johnny Blockhead]

how long does your server stay existant after it expires?

mine expired yesterday and i couldnt renew it as the person that owns the server was at working

how long does it last?

I'd say about a day or two. Not really shure.

Small Update

Can we change the limit with the console disabling thing?

[Ephialtes]

how long does your server stay existant after it expires?

mine expired yesterday and i couldnt renew it as the person that owns the server was at working

how long does it last?

Your server will be suspended after 24 hours then it'll be terminated after 48 hours. If you're intending to pay and don't want it to be terminated please drop us a ticket ASAP and I'll extend the termination to give you some time.

Can we change the limit with the console disabling thing?

No -  the limit is intended to make sure your console spam doesn't affect other users on the node. Letting people arbitrarily change that would defeat the objective.

[Plexious]

Will running trace(); instantly disable your console output if used on a busy server?

[Ephialtes]

Will running trace(); instantly disable your console output if used on a busy server?

Pretty much yeah. We'd initially intended to disable trace just because it can cause so much load. I can definitely look at extending the period over which there needs to be high load for output to be disabled so that small bursts of trace use is permitted.

[SWAT One]

Pretty much yeah. We'd initially intended to disable trace just because it can cause so much load. I can definitely look at extending the period over which there needs to be high load for output to be disabled so that small bursts of trace use is permitted.

It is possible to have a "safe mode" type of server option where trace is enabled, but performance is significantly decreased and such for development purposes?  Or is this too much work?

[Plexious]

Pretty much yeah. We'd initially intended to disable trace just because it can cause so much load. I can definitely look at extending the period over which there needs to be high load for output to be disabled so that small bursts of trace use is permitted.

You could try and work around high console output instead of disabling it and causing trouble for many people.

[Ephialtes]

You could try and work around high console output instead of disabling it and causing trouble for many people.

There's no "working around" something that seriously degrades your server's performance. If you have an add-on that's spamming the console 10 times a second that's not something I'd be willing to "work around" - that's a very poorly maintained server that needs to be fixed or it can't benefit from the functionality we offer.