I have noticed in the AMP Server log that the following error appears very frequently and I am unsure as to its meaning.  Anyone encountering the same thing?

[2012-08-21 03:52:33 -0400] AgentRead: Error timeout before reading

[2012-08-21 03:52:33 -0400] [Client Disconnected] FC5B8D16-FECD-4443-8184-70E0CF6B4756 (

[2012-08-21 03:52:53 -0400] [New Connection Accepted], socket: 70, num accepts: 3771

[2012-08-21 03:52:53 -0400] [New Connection Accepted], socket: 70, num accepts: 3772

[2012-08-21 03:52:54 -0400] Connect: version (6); machineId (FC5B8D16-FECD-4443-8184-70E0CF6B4756); plugins (0,2,4,6,5); agentInfo (ver=5.3.53177&os=windows&arch=x86&host=CHX123DT123&ip=


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



What operating system is this happening on?

I saw something like this on a Win8 test system. It didn't like the built-in NIC, but wireless worked fine, so maybe give that a try.

Answered 08/21/2012 by: jknox
Red Belt

  • The error appears in the K1000 AMP Server log for a number of our systems running under either Windows XP SP3 or Windows 7. There does not appear to be any trend related to specific NIC models as this is occuring on a large span of NIC models across our desktops and laptops. No wireless used at our site at this time.
    • I've seen that happen with desktops before where the AMP socket times out and creates a new connection.

      It sometimes causes duplicate inventory, so you will want to check that: http://www.kace.com/support/resources/kb/article/Understanding-and-Dealing-With-Duplicate-Machines-In-Inventory?action=artikel&cat=9&id=673&artlang=en
  • Is it related to a network segment or vlan?
Please log in to comment

This error usually comes under high load conditions on server when server might reject some agent connections.

You can check the "Connections" graph in the "System Performance" logs on server to see if the connections were very high at that time when error occured.

This issue is going to be addressed in future release. However, If you are observing this problem frequently, then please contact Support. They can apply a patch to address this issue.




Answered 08/21/2012 by: AbhayR
Seventh Degree Black Belt

Please log in to comment