ik he wasn't but im still getting sick of these sarcastic comments and the repeat comments. maybe u guys have a great humor but im not in the mood for it today..
*cough** u for got something in that codeline... its actually Run lol lol run run ROFLMAOLALOLMAO run
News guys, it shall be running like a horse again. We found the issue, like 3 hours ago one of our auth servers got an new power supply. Thats where the error happened, as the new booted auth had from then on a date of 27th and a time +5h from right now. This messed all sessions up as this was the main AUTH Server, which will be contacted at first at any connection, if that server is completely down then another 2 servers will jump in. However once the server was up with the new power supply unit and the messed up clock, the issues began, we had quite a lot to look at to find that .... sorry for the downtime.
I believe we fixed it for good now. Not seeing any invalid session messages pop up anymore (at least in our logs, there will be a few who get one or two for the next 5min, but should resolve itself afterwards) What happened: One of our servers had a PSU fail (which was replaced earlier today [~5hrs ago]), however due to the way we manage our auth system, none of us realized that it had even died. (Win yes?) With that said, it had reset a few things, which showed us some bugs in our auth implementation. They've been fixed, so this type of failure shouldn't happen again in the future. If you're still having issues, please, let us know.
As bossland said; it really was a silly issue. We've taken the necessary steps to make sure this type of failure won't happen again.
Awesome....and I hate those silly issues too. You could have looked for days for something like that. Good eye!
