In the K1000 AMP Server Log, what is the meaning of the following error notification: "AgentRead: Error timeout before reading"
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 (10.1.20.106)
[2012-08-21 03:52:53 -0400] [New Connection Accepted] 10.1.20.106:1609, socket: 70, num accepts: 3771
[2012-08-21 03:52:53 -0400] [New Connection Accepted] 10.1.20.106:1611, 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=10.1.20.106&mac=00-18-FE-6E-08-CC)
Answers (2)
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.
Comments:
-
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. - Sartos1 12 years ago
-
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 - jknox 12 years ago
-
Is it related to a network segment or vlan? - SMal.tmcc 12 years ago
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.
-Abhay