Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
02-22-2021 07:47 PM - edited 03-25-2021 08:57 PM
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.
02-23-2021 09:39 AM
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:
Let me know if this was helpful!
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
03-25-2021 10:16 AM
Hi Ryan, But we don't have any machine agents running in our host machines.
03-25-2021 12:57 PM
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.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
09-08-2022 02:39 AM
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.
09-28-2022 10:18 PM - edited 09-28-2022 10:22 PM
First, make sure the node name is not already registered with the Controller using the same hostname.
If it is, you can:
If the node name is NOT already registered with the Controller using the same hostname, check the node associated with the warning.
10-06-2022 10:28 PM
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:
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form