Server Downtime & Read Time Outs | Server News | Forum

UPDATE 3 (06/28)

Over the past two days, our hosting provider has moved several MC servers off to other servers in order to bring server loads within reasonable limits - they generally strive for a peak of 70-80% CPU. Our server's performance seems to have returned to normal, although we are still getting occasional bursts of overload messages during different parts of the day. I'm keeping them informed along with detailed logs in order for them to narrow down potential culprits (obviously not us ). So for now, we are backing off on the notion of moving to another server unless a situation absolutely warrants it; furthermore, we have more important projects underway that we'd rather see completed.

We are still getting bursts of overload messages during different parts of the day. I'm working with the hosting provider in hopes of identifying the culprits

UPDATE 2

The frequent read time outs have abated for the most part, although they are not completely gone. We did experience a server deadlock around 0:25 AM EST that forced us to reboot causing a minor rollback to 10 minute prior. Please be aware that we do not restore what wasn't saved. There is no need to pester staff about it. Obviously its embarrassing when such things happen, especially when they are not under our control, but we forge on.

UPDATE

FragNet has assured me that they are working on reducing our server's load and that we should start seeing an improvement over the next few hours (crossing fingers). We will give it 48 hours to see if things return to normal. If not, we will consider their offer to move us to another server.

---------------------------------------------------------

Our hosting provider has fessed up that our host server is overloaded, although that does not explain the sudden increase in read times outs over the past 8 hours. They've offered to move us to a higher-powered server, which we will gladly entertain. Unfortunately, this couldn't have any worse timing.

I am awaiting a response from FragNet to get an idea of timing and availability to make this server move happen. This isn't our first dance, but we still have to hedge our bets. For now, we'll have to suffer the read timeouts as best as we can.