Re-occuring SEVERE errors in controller logs -- "failed to processes the request"

[CommunityUser]

I'm trying to stop some re-occuring errors from showing up in the controller log. Could anyone tell me what the following errors mean and how to stop them from occuring/fix the problem that causes them?

[#|2016-08-30T15:04:24.895-0500|SEVERE|glassfish3.1.2|com.appdynamics.AGENT.AGENT_CONFIGURATION|_ThreadID=62;_ThreadName=Thread-5;|Failed handling transaction config request.  Machine  Id: 553  Node Id: 29  Application component node id:29 is not associated to machine id:553|#]

[#|2016-08-30T15:04:50.993-0500|SEVERE|glassfish3.1.2|com.appdynamics.AGENT|_ThreadID=126;_ThreadName=Thread-5;|l failed to process the request URI:/controller/instance/360/systemagentpolling|#]

[Arun_Dasetty]

Hi,

the first error means that some MachineAgent is trying to register to agent node in UI but due to host conflict issues it could be resulting in registratio failure, please start agent with correct uniquehost id arguments and validate config as per docs scenario whether no agents are trying to register with different host name but same node OR machine agent is trying to auto register with no node-name to target app but host name conflict raised:

https://docs.appdynamics.com/display/PRO41/Configure+Multiple+Standalone+Machine+Agents+for+One+Mach...

[CommunityUser]

How about the second error? I also got this error.

[CommunityUser]

In case anyone else looks this up... I opened a case with Support about the "SEVERE error failed to process the request." This was their reply--

"The message was due to aggressive SIM check and logging. This has been fixed in 4.2.6.2 & 4.2.8 (yet to be released). The message can be ignored if you don't see any issue."