Removing client loop - major issue

[John Adams]

Yeah yeah, another big issue from JA... but this is a big one that I cannot figure out, and it's happening more and more on the Release build - never see it on Debug.

Basically, what I see in the console (now) is normal usage, with a few extra debug-looking lines:

(started right after Wed, 1 Apr 2009 03:46:58 UTC)

Code: Select all

Connected to LoginServer: eq2emulator.net:9100
67.11.231.175:9100: TCPConnection::RecvData(): Connection timeout
Connected to LoginServer: eq2emulator.net:9100
AddAuth: 987 Key: 1238556050
135239590 New client from ip: 216.119.187.159 port: 61466
135239590 New client from ip: 216.119.187.159 port: 61466
Combined Packet!
Combined App Packet!
World: Removing client from ip:216.119.187.159 port:61466
Removing connection
AddAuth: 987 Key: 1238557494
136681240 New client from ip: 216.119.187.159 port: 61175
136681240 New client from ip: 216.119.187.159 port: 61175
Combined Packet!
Combined App Packet!
World: Removing client from ip:216.119.187.159 port:61175
Removing connection
Delete char request: 987 1828
Name check on: Omibam
Resp: 1
AddAuth: 987 Key: 1238557618
136805463 New client from ip: 216.119.187.159 port: 61731
Adding client to waiting list...
136805463 New client from ip: 216.119.187.159 port: 61731
Combined Packet!
Combined App Packet!
Combined Packet!
ZoneAuth: Access Key, 1238557618, Character Name, Omibam, Account ID, 987, TimeStamp, 1238557618
Loading new Zone 'QueensColony'
Loaded Incompatible version : 955
694 NPC(s), 129 Object(s), 0 Widget(s), 38 Sign(s), 127 GroundSpawn(s).
Shutting Down Zone 'QueensColony'
OP_ClientIdleBeginMsg Received 0x017a
   0: 00 00                                              | ..
OP_ClientIdleBeginMsg Received 0x017a
   0: 01 00                                              | ..
OP_ClientIdleBeginMsg Received 0x017a
   0: 01 00                                              | ..
OP_WorldPingMsg Received 0x0175
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731
World: Removing client from ip:216.119.187.159 port:61731

then the world goes into a flippin tizzy spamming

Code: Select all

World: Removing client from ip:216.119.187.159 port:61731

Literally, 150mb if a text file before I finally looked at the log and caught it. I am PM'ing you the log, LE, because it's just too large to bother attaching here. I don't think you'll see anything more than this, but at least you can see what a big issue this can be.

I am not sure if there were 2 clients connected at this time, but the end lines of the log show the same removing client message for 2 different IPs, and the console reports 2 Zones, 2 Clients when I killed it.

[LethalEncounter]

That last line just spammed continuously? I should be able to track it down.

[John Adams]

Yessir. That one line did, but after the second client disconnected, then it altered between the two... doing the first IP a dozen or so times, then the second, then back and forth til I found the server doing this - and killed it.

I can't say it prohibited new client connections - kinda assuming that.

[LethalEncounter]

I found one tiny issue, but how that caused what you pasted I'm not sure. Please let me know if this continues after you update.

[John Adams]

I have not seen this in weeks, so I am considering it resolved for now. Thanks LE!