We fixed ark70, one of the South Africa machines. It's all good again!
One of our South Africa machines, ark70, is down for about an hour. It had some hardware break and we are replacing it.
One of our servers, ark55, froze up this morning and was rebooted. Everyone's game servers should be back now.
Back in October, Studio Wildcard did a brief Halloween Event, which was implemented in a very unusual way that they had never done before. Rather than add a command line flag as they had in the past, they published a beta branch of the game on Steam that you had to download by passing "-beta halloween" to steamcmd. Some people saw references to "-beta halloween" on forums and thought that all we had to do was add this command line flag for their game. Those people then got mad at me for not doing that. =(
Our system works by just downloading the game from Steam once onto each machine, and then copying that into everyone's home directory. This was designed to go faster and save bandwidth, but it means that we can't just download a different branch from Steam for a particular customer. I would be happy to change the system, but since that event only ran for several days, the effort would have been moot by the time it was done.
I guess I should have done it after all, because Studio Wildcard just dropped this bomb on us again. They're running a Christmas event, which is available in the beta branch "-beta holidayevent". As before, the forums are filled with mistaken posts from people who think that this is a command line flag for Ark, when it's actually one for steamcmd.
Bottom line, I screwed up again and we can't do the event. I do deserve some blame for this one because I didn't fix our system after the failed Halloween event. But I think Studio Wildcard deserves some blame too, since they dropped this on us with no warning.
I'll have to change our system to be able to download these beta branches and make them available to people, since it sounds like this won't be the last time.
So someone at the data center mistakenly unplugged it while racking another machine. Sorry guys! =(
Everything should be back online now!
We just had a machine (known to us as ark71) die within the last hour. We're looking into it.
The new map is out, and the level of demand from our customers is stunning. The dedicated server patch has been downloaded onto all of our machines, and we're in the process of rebooting lots of Ark servers. There are hundreds of you guys eagerly mashing the restart button as well, which is not making things go any faster! =)
If past releases are any indication, we'll probably be seeing more fixes and reboots rolling in over the next few days. Please be patient! These upgrades tend to be bumpy, but it all gets sorted out eventually.
I noticed you guys are pretty excited about the new Aberration map! I know as much as you do at this point -- it's supposed to come out at 8AM (California time). When Studio Wildcard makes the dedicated server update available, all of our servers will automatically start downloading it. Everyone else in the world will be doing the same thing, so expect some slowness here.
It should be ready about an hour or two after that, and we will add the map to the maps list selector at that time.
All machines are online! Sure has been a hard week for me! Good night! =)
The week of bizarre network outages continues! We currently have 5 machines in the Western Europe region that are down. The network guys are investigating!