Question about "Waiting for server response"

[Tiger205 48]

I just want a clear answer - why some of the servers are constantly fucked so basicly people can't play on them? I mean I see a lot of empty servers in the browser and when I join in to check what's going on it just hangs on "Waiting blabla". Is this caused by the server not being restarted often enough or something completely different? I may have missed the answer to this so that's why I'm asking it here and now.

[Freeborne (DayZ) 7]

I don't know for certain. What I have noticed though was over the past 24-48 hours, there was frequent errors in Hive and HiveAuth, and sometimes these apps could not communicate with the remote SQL server either. I suspect the server was getting hit too hard and refusing some of the connections and data we were sending it.

My other assumption, is that Hive and HiveAuth are not programmed to be forgiving when the central Hive server is unreachable, so the program will still run, and ARMA2 server will keep running, but the actual SQL connection and data will not go through, causing issues like "Waiting for Server Response".

So some server admins are restarting their game server automatically when it crashes, but they need to manually restart HIVE too, even though the app hasn't crashed, it needs to re-authenticate with Hive again.

I played on a few servers, and they had the same problem with Waiting for Server Response. The game server would crash and restart automatically, but the problem persisted. On our servers, we kept manually restarting the Hive apps and it fixed our problems, but they would return after a while (again, because I believe central Hive was overloaded)

[Tiger205 48]

Well this looks like a plausible cause but some servers are broken all the time. Do the admins completely forget about their servers or something? Especially DE and FR servers, at least for me.

[Freeborne (DayZ) 7]

Yes, probably. If you play on those servers, look for an in-game admin, or go on their TeamSpeak and see if you can find one. If several players have same problem, it's probably something they can fix by restarting server or Hive apps.

There's also players who install 1.5.6 over 1.5.7 and then join a server. They get the msg "you need to update your files", so they then copy 1.5.7 back again, overwriting 1.5.6. Then they rejoin and get straight back in the servers.

I believe the reason in those cases is the players have some corrupt data in their gear (I see it often in the Hive logs), so going back to 1.5.6 sort of clears out that corrupted data, so that when they upgrade again to 1.5.7 they have a nice clean inventory of gear and the server processes that quickly.