TrinityCore/TrinityCore — Issue #4577: Pinging goes into insane loops and disconnects everyone
Author: henhouse
Created: 2012-01-01 22:22:51+00:00
State: open

Tested on latest revision with Windows.

As I discussed here: http://www.trinitycore.org/f/topic/5294-why-is-trinity-pingbombing-itself/

The server goes into these absolutely insane loops where it starts pinging itself anywhere from 15-30 times a second. Literally DDoSing the SQL server and disconnecting all players. I commented out the code in World.cpp but then the "Next game event check in %u seconds." would go into loops and spam too and still disconnect players.

Fresh TrinityCore, fresh Trinity Database and up-to-date. Why is this happening?

Example of what the log file would look like:

2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:15:59 Next game event check in 2642 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:00 Next game event check in 2641 seconds.
2012-01-01 17:16:01 Next game event check in 2640 seconds.
2012-01-01 17:16:01 Next game event check in 2640 seconds.
2012-01-01 17:16:01 Next game event check in 2640 seconds.
2012-01-01 17:16:01 Next game event check in 2640 seconds.
2012-01-01 17:16:01 Next game event check in 2640 seconds.

This is after I commented out the "Ping MySQL to keep connection alive" in World.cpp. Problem still persisted with game events.

Also, yes my MaxPingTime is still on the default 30.