Author Topic: Anyone Know What's Going on with CBMHost?  (Read 2486 times)

I sometimes choose the older saves because sometimes the build somehow messes up, so when I use the older autosave, it actually has a better version (My autosaving time is around 5 mins, but a lot a things happen during that time)

  • People replacing our correct version of RTB

This is a likely cause, I've been noticing a few servers running the old version of RTB that attempts to post to the RTB servers, which no longer exist and therefore causes the TCP socket buffer to become full up due to the fact that it does not close the sockets after they fail to connect, rendering any connections to the server unable to connect after it fills up. Also, my Pingdom reported 2 minutes of downtime between 6:29PM EDT and 6:31PM EDT. It's done that for three days in a row now, but never more then 2 minutes. So, I need to find out if it's the provider's network going down or a small DoS, both of which are possible.

/dediLoad auto0

There is also other auto files that goes up to 5, I think the lower, the more recent

Just commenting on this, the number of save archives can be increased, the default is 5 before it starts to overwrite the old files, but it can be changed to have 20, 50 or whatever you like.
« Last Edit: April 22, 2014, 09:44:54 PM by Cowboy6 »

but it can be changed to have 20, 50 or whatever you like.
Well, you'll end up with gigabytes of old .bls files.

Well, you'll end up with gigabytes of old .bls files.

No, because I have to mod it, it's not user changeable at this point. The average save file is less then 2MB in size anyway and I have two 2TB 7200RPM Barracuda drives in it, so space is not really an issue at this point.

No, because I have to mod it, it's not user changeable at this point. The average save file is less then 2MB in size anyway and I have two 2TB 7200RPM Barracuda drives in it, so space is not really an issue at this point.
what servers were effected?

what servers were effected?
The good thing, I don't think mine was affected. I did have to restart mine though to fix the master server posting though.