What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Auth server kicks bots off randomly

Status
Not open for further replies.
pushedx, if that is auth issue, why u just dont do reconnections attempts for bot/auth server?
 
Thanks for the logs, going over it with the auth team soon!
 
My log is almost same "Authentication server ... bla,bla" , but check this out: event viewer-system - warning 1014 - "Name resolution for the name auth.eu.buddyauth.com timed out after none of the configured DNS servers responded". That issue is only for running duet poe+eb.

edit
 

Attachments

Last edited:
My log is almost same "Authentication server ... bla,bla" , but check this out: event viewer-system - warning 1014 - "Name resolution for the name auth.eu.buddyauth.com timed out after none of the configured DNS servers responded". That issue is only for running duet poe+eb.

Log or never happend.
 
All my bots just got kicked off now, same error in logs:

2015-11-02 00:09:19,826 [25] DEBUG CustomLogger (null) - [FinishCurrentAction] Waiting for the action to finish Move.
2015-11-02 00:09:20,006 [25] DEBUG CustomLogger (null) - [LootItemTask] Now attempting to interact with the item. This is the #1 attempt.
2015-11-02 00:09:20,007 [25] DEBUG CustomLogger (null) - [InteractWith] Now attempting to highlight 5453.
2015-11-02 00:09:20,389 [25] DEBUG CustomLogger (null) - [InteractWith] Now attempting to interact with 5453.
2015-11-02 00:09:20,592 [25] INFO CustomLogger (null) - [AreaStateCache] The location 5453 [Chain Hauberk] is being removed because the WorldItem does not exist.
2015-11-02 00:09:20,933 [25] DEBUG CustomLogger (null) - [LootItemTask] The current item to loot is [5453] Chain Hauberk at {521, 313}. We have been on this task for 00:00:01.4909364 and have been attempting to interact for 00:00:00.8119635.
2015-11-02 00:09:20,933 [25] INFO CustomLogger (null) - [RemoveItemLocation] The location 5453 [Chain Hauberk] is being removed.
2015-11-02 00:09:22,492 [25] DEBUG CustomLogger (null) - [FinishCurrentAction] Waiting for the action to finish Summon Raging Spirit.
2015-11-02 00:09:23,520 [25] DEBUG CustomLogger (null) - [FinishCurrentAction] Waiting for the action to finish Summon Raging Spirit.
2015-11-02 00:09:25,189 [8] ERROR CustomLogger (null) - Error while communicating with authentication server: System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:09:59.6552735'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.SocketConnection.ReadCore(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, Boolean closing)
at System.ServiceModel.Channels.SocketConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.DelegatingConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Buddy.Auth.SR.IA.Do(Byte b, Object[] args)
at ?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????(????????????????????????????????????????? , Object[] )
at ?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????(Object[] )
at ?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????.?????????????????????????????????????????(????????????????????????????????????????? )
2015-11-02 00:09:25,193 [8] ERROR CustomLogger (null) - Authentication server communication failed: Invalid Session
2015-11-02 00:09:25,248 [8] INFO CustomLogger (null) - The bot is now logging out the client due to an auth issue.
2015-11-02 00:09:25,290 [8] DEBUG CustomLogger (null) - [ActivateEscapeState] !IsEscapeStateActive. Attempting to open it.
2015-11-02 00:09:31,001 [8] DEBUG CustomLogger (null) - LogoutToTitleScreen returned None.
 
Some people in other bots are noticing it now too, so it's definitely being looked into.

Beta #1163 was just pushed with some additional logging and the auth service itself got a logging update.

Please attach new logs from #1163 and on to this thread.
 
Status
Not open for further replies.
Back
Top