Application component node id:13222 is not associated to machine id:161132

[Anantnag.Tirlapur]

Can someone please let us know what this error means - 

Application component node id:13222 is not associated to machine id:161132

These are coming in agent logs.

[Ryan.Paredez]

Hi @Anantnag.Tirlapur,

I found an older post that mentioned this:

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 registration failure, please start the agent with correct uniquehost id arguments and validate config as per docs scenario whether no agents are trying to register with different hostname but same node OR machine agent is trying to auto-register with no node-name to target app but hostname conflict raised:

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

Let me know if this was helpful!

[Anantnag.Tirlapur]

Hi Ryan, But we don't have any machine agents running in our host machines.

[Ryan.Paredez]

Hi @Anantnag.Tirlapur,

Thanks for letting me know. I don't have any more info at this time. Let's see if the Community can jump in and help.

[Dietrich.Meier]

Hi Anantnag and Ryan

We are experiencing the exact same issue and currently not getting anywhere with AppD support on this.

The agent reports in until the first redeployment is done and then stops with the same error the whole time.
(...Application component node id:1634... is not associated to machine id:36314...)

Process followed for cluster agent setup:
https://docs.appdynamics.com/appd/21.x/21.2/en/infrastructure-visibility/monitor-kubernetes-with-the...

Process followed for Java Agent:
https://docs.appdynamics.com/appd/22.x/latest/en/application-monitoring/install-app-server-agents/ja...

Hope someone has found the solution to this one. 

[Harris.Ashraf]

First, make sure the node name is not already registered with the Controller using the same hostname.

If it is, you can:

• Change the node name to a unique name
• Set the APPDYNAMICS_AGENT_UNIQUE_HOST_ID Environment Variable to proide a unique host name for the system the agent is running on.

If the node name is NOT already registered with the Controller using the same hostname, check the node associated with the warning.

• If you can confirm the snapshots are collecting on the current node, and observe the expected agent uptime, it could be the issue is instead related to a hold-over from the node's registration on the Controller for identification.
• If your monitoring is working as expected, the warning itself can be ignored without resulting in any issues

[Dietrich.Meier]

Hi Harris

Thanks for the input.
We had a WebEx call with AppD support after my previous post and got things sorter out.
Check the comments from AppD following the call.

Observations and actions performed: 

• During the call, we noticed some incompatibilities in the versions of cluster-agent and operator.
• Upgraded both to latest versions and noticed cluster agent deployed fine and instrumentation was happening.
• But we noticed 2 nodes getting created for each application, although there is only one pod deployed per application.
• After inspecting the application, it turned out that the customer had already applied instrumentation at the Dockerfile. The image itself is coming with instrumentation and top of that, they were enabling auto-instrumentation.
• We had suggested them to remove the instrumentation in either of the place.