-
Bug
-
Resolution: Invalid
-
None
-
Minecraft 1.7.5
-
None
-
Linux Server
-
Unconfirmed
I host hundred of Minecraft servers and have randoms bugs regarding the authentication process to Mojang's servers.
The strange thing is a reboot can solve the bug.
After deeply troubleshooting the issue, I came to the conclusion that it comes from the auth backend server used by the Minecraft server's to authenticate players.
As mentionned, it seems to use a single server, since the HTTP request are replied with the following return code :
HTTP 503, backend server is at capacity
The main issue is the server will always try to contact the exact same backend server until the next reboot. This is not logic at all since you're using a load balanced system to provide authentication for all minecraft's servers around the world.
The point is, why the server would keep trying to authenticate players throught the same backend server, even if it looks overloaded ?
Is there any sticky session system on your side ? If so, a cookie could be responsible of it ?
It's also important to note that it can work well for some servers, some can have this issue each day, there isn't a single behavior.
Any versions of Minecraft (1.5/1.6/1.7) and types (Vanilla, Bukkit, Spigot, MCPC+) can have this issue.
Technical details :
- OS : Debian 7.3 64 bits (amd64 platform)
- Kernel : 3.11.10
- Java : OpenJDK 7u25-2.3.10-1~deb7u1
- Java version : 7
- Additional details : we're using Java Security Manager to avoid access to unauthorized files/folders on the system to java (such as /home, /, /etc, ...)
Thanks in advance for further informations in debugging. Don't hesitate to ask me for details if needed.