Return of Reckoning

Posted: **Wed Apr 13, 2016 12:01 am**

I honestly don't know if anyone else has this issue, but I keep getting dc'd from the server a lot. There seems to be no rhyme nor reason to events that trigger it. I've googled the symptoms in the login log with no success. I've also searched in here and trawled through various posts, no joy.
I can play, so that's great, but these random dc's are doing my head in. Can any of you smart peeps make sense of this code snippet from my logindate.log file

Code: Select all

[2016/04/13 00:45:44] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2016/04/13 00:45:44] Attempting authentication using session token
[2016/04/13 00:45:44] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2016/04/13 00:45:44] MythLogin::LoginClient::Connect: Attempting connection to 178.32.58.46:8048
[2016/04/13 00:45:44] Active Sockets:  Host [0] Client [1]
[2016/04/13 00:45:44] MythLogin::LoginClient::HandleVerifyProtocolReply: Received protocol verification reply from server
[2016/04/13 00:45:44] MythLogin::LoginClient::Authenticate: Attempting authentication with session token
[2016/04/13 00:45:44] MythLogin::LoginClient::HandleAuthSessionTokenReply: Received session auth reply from server
[2016/04/13 00:45:44] MythLogin::LoginClient::SendEventNotification: Sending notification of event [9] to server
[2016/04/13 00:45:44] MythLogin::LoginClient::GetAccountProperties: Requesting account properties from server
[2016/04/13 00:45:44] MythLogin::LoginClient::HandleGetAccountPropertiesReply: Received account properties list reply from server
[2016/04/13 00:45:44] MythLogin::LoginClient::GetClusterList: Requesting cluster list from server
[2016/04/13 00:45:45] MythLogin::LoginClient::HandleGetClusterListReply: Received cluster list reply from server
[2016/04/13 00:45:45] MythLogin::LoginClient::GetCharacterSummaries: Requesting character list from server
[2016/04/13 00:45:45] MythLogin::LoginClient::HandleGetCharListReply: Received character list reply from server
[2016/04/13 00:45:45] MythLogin::LoginClient::ConnectionClosed: Connection to server closed.
[2016/04/13 00:45:45] MythLogin::LoginClient::Teardown: Exhausted all servers in cycle.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.
[2016/04/13 00:45:45] TCPNETSet::OSProcess EnumNetworkEvents call failed! Error code = 10038. Treating socket as closed.

Posted: **Wed Apr 13, 2016 11:49 pm**

Any ideas at all would be welcome....

Posted: **Thu Apr 14, 2016 12:00 pm**

The majority of people experience disconnects from the server and/or crashes to desktop. The most likely culprit is caused by corrupt/malformed packets between client and server. Until we've managed to identify the specific causes for these and rectify it, this will be a common issue.

Posted: **Thu Apr 14, 2016 12:59 pm**

Ah, ok cheers Elven for taking the time to reply. It's much appreciated.
So, I assume that there#s nothing specific in the log that indicates anything fixable on my end

Is there anything at all that I could install on my end & submit to assist in the debugging? I stick quite a few hours in online, and I'm more than happy to do anything that I can to help.

Posted: **Thu Jun 16, 2016 7:52 am**

This is not the symptoms of the random dc' from malformed packets.
This is a symptom of an issue within the authentication server not the world server.

(Note the times stamps on your posted logs. 2 seconds; the game would not have loaded in by then)

The error descriptor given is vague and does not correspond to the code (not having access to exactly what is coded to cause such problems, all one can assume is the authentication server is under-load, memory leaking, etc. as this is network related.

As a side note: (Maybe this issue relates to the random in world server dc'. perhaps the character server is not returning correct information to the world server which is then the root of malforming packeting the players joining the party with new guild information for instance)

Posted: **Thu Jun 16, 2016 11:43 am**

nibbles wrote:This is not the symptoms of the random dc' from malformed packets.
This is a symptom of an issue within the authentication server not the world server.

(Note the times stamps on your posted logs. 2 seconds; the game would not have loaded in by then)

The error descriptor given is vague and does not correspond to the code (not having access to exactly what is coded to cause such problems, all one can assume is the authentication server is under-load, memory leaking, etc. as this is network related.

As a side note: (Maybe this issue relates to the random in world server dc'. perhaps the character server is not returning correct information to the world server which is then the root of malforming packeting the players joining the party with new guild information for instance)

Nope, already solved. None of the above.
Turns out it was as a result of the addon "nerfed buttons". If I alt-tab out of game for any reason and then continue to play, then close the game it would result in this error. If I play without alt-tabbing, then the game closes normally. Debugged by removing NB (problem goes away) and then reinstalling NB (duplicate problem).
Solution was simply to use my tablet for any internet activity while in-game and not alt-tab.

Return of Reckoning

Daily multiple disconnects "treating socket as closed"

Daily multiple disconnects "treating socket as closed"

Re: Daily multiple disconnects "treating socket as closed"

Re: Daily multiple disconnects "treating socket as closed"

Re: Daily multiple disconnects "treating socket as closed"

Re: Daily multiple disconnects "treating socket as closed"

Re: Daily multiple disconnects "treating socket as closed"