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
04-22-2017 08:51 AM
Hi
There seems to be very little information on the Internet or Appdynamics documentation on troubleshooting agent registration issues.
I'm trying to register a new server agent on Linux with Appdynamics I get a very obscure registration error when running the agent:
---
[UriConfigPoller] 20 Apr 2017 10:57:21,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/ to see if it is readable.
[system-thread-0] 20 Apr 2017 10:57:21,160 DEBUG RegistrationTask - Running registration task
[system-thread-0] 20 Apr 2017 10:57:21,168 WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
[system-thread-0] 20 Apr 2017 10:57:21,168 DEBUG RegistrationTask - Encountered error during registration.
com.appdynamics.voltron.rest.client.NonRestExcepti
---
The agent I'm using was generated from the Appdynamics enterprise dashboard and uploaded to the linux server.
Things I've checked:
- Network connectivity: packet flow at tcp level is fine between agent and server.
- Licensing: Licensing is valid
- hostname/unique agent id: as a test , set manually using the result of "hostname" command.
There seem to be no other appdynamics guides on how to troubleshoot this in further detail. Past forum posts seem to yield low quality answers.
More complete debug log dump as follows:
----
[UriConfigPoller] 20 Apr 2017 10:56:51,117 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/log4j.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:56:51,117 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:56:51,117 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/controller-info.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:56:51,117 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:21,117 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/log4j.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:21,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:21,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/controller-info.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:21,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/ to see if it is readable.
[system-thread-0] 20 Apr 2017 10:57:21,160 DEBUG RegistrationTask - Running registration task
[system-thread-0] 20 Apr 2017 10:57:21,168 WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
[system-thread-0] 20 Apr 2017 10:57:21,168 DEBUG RegistrationTask - Encountered error during registration.
com.appdynamics.voltron.rest.client.NonRestExcepti
at com.appdynamics.voltron.rest.client.VoltronErrorDe
at feign.SynchronousMethodHandler.executeAndDecode(Sy
at feign.SynchronousMethodHandler.invoke(SynchronousM
at feign.ReflectiveFeign$FeignInvocationHandler.invok
at com.sun.proxy.$Proxy80.registerMachine(Unknown Source)
at com.appdynamics.agent.sim.registration.Registratio
at java.util.concurrent.Executors$RunnableAdapter.cal
at java.util.concurrent.FutureTask.runAndReset(Future
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$Worker.run
at java.lang.Thread.run(Thread.java:745)
[UriConfigPoller] 20 Apr 2017 10:57:51,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/log4j.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:51,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:51,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/controller-info.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:57:51,118 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:58:21,119 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/log4j.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:58:21,119 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/logging/ to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:58:21,119 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/controller-info.xml to see if it is readable.
[UriConfigPoller] 20 Apr 2017 10:58:21,119 DEBUG UriConfigProvider - Checking uri file:/opt/appdynamics/conf/ to see if it is readable.
[system-thread-0] 20 Apr 2017 10:58:21,160 DEBUG RegistrationTask - Running registration task
[system-thread-0] 20 Apr 2017 10:58:21,169 WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
[system-thread-0] 20 Apr 2017 10:58:21,169 DEBUG RegistrationTask - Encountered error during registration.
com.appdynamics.voltron.rest.client.NonRestExcepti
at com.appdynamics.voltron.rest.client.VoltronErrorDe
at feign.SynchronousMethodHandler.executeAndDecode(Sy
at feign.SynchronousMethodHandler.invoke(SynchronousM
at feign.ReflectiveFeign$FeignInvocationHandler.invok
at com.sun.proxy.$Proxy80.registerMachine(Unknown Source)
at com.appdynamics.agent.sim.registration.Registratio
at java.util.concurrent.Executors$RunnableAdapter.cal
at java.util.concurrent.FutureTask.runAndReset(Future
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$Worker.run
at java.lang.Thread.run(Thread.java:745)
---
Troubleshooting notes:
Trying to register a new agent with the controller fails, even though I am using a superuser account to generate the agent zip file and I have more than 50 agent licenses (i've also disabled SIM on the agent side):
Logs on the agent show:
[system-thread-0] 22 Apr 2017 14:19:06,786 WARN RegistrationTask - Encountered error during registration. Will retry in 60 seconds.
[system-thread-0] 22 Apr 2017 14:19:06,786 DEBUG RegistrationTask - Encountered error during registration.
com.appdynamics.voltron.rest.client.NonRestExcepti
at com.appdynamics.voltron.rest.client.VoltronErrorDe
at feign.SynchronousMethodHandler.executeAndDecode(Sy
at feign.SynchronousMethodHandler.invoke(SynchronousM
at feign.ReflectiveFeign$FeignInvocationHandler.invok
at com.sun.proxy.$Proxy80.registerMachine(Unknown Source)
at com.appdynamics.agent.sim.registration.Registratio
at java.util.concurrent.Executors$RunnableAdapter.cal
at java.util.concurrent.FutureTask.runAndReset(Future
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ScheduledThreadPoolExecutor$S
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$Worker.run
at java.lang.Thread.run(Thread.java:745)
---
NOTE: registration also fails if SSL is turned off and non-https port is used to connect to the controller.
Additional data point, in the controller logs I see these entries, suggesting some kind of authentication error between agent and controller:
---
[#|2017-04-22T14:50:57.556+0000|INFO|glassfish 4.1|com.singularity.ee.controller.auth.AuthRealm|_
[#|2017-04-22T14:50:57.556+0000|INFO|glassfish 4.1|javax.enterprise.system.core.security|_ThreadI
Authentication refused for [singularity-agent@customer1_xyxyxyxyxyxyxyxyxyxyx
[#|2017-04-22T14:50:57.556+0000|INFO|glassfish 4.1|javax.enterprise.system.core.security.com.sun.
----
However, this agent was built through the UI and there is no indication of a user or credentials that may be needed ..
Solved! Go to Solution.
04-23-2017 01:00 AM
Dear Traiano
Sorry for the poor experience you had with that forum. If you are a paid customer and want to drive this through support, you can use the AppDynamics portal to log a ticket.
However, i may have an idea for your problem. Just a confirmation: is that 4.3?
If yes, on 4.3, when generating the Machine Agent using the Getting Started Wizard, the account name used is the Global Account Name, instead of the Account Name. So you need to change that in the controller-info.xml file.
Let us know
Best
JB
04-23-2017 01:43 AM
Hi JB
Thanks for your response.
We're using a licensed version of AppDynamics Version 4.3.0.3, build 147.
I've confirmed we're using the global account name in controller-info.xml.
I've also confirmed we're using the corresponding license key.
However the issue persists. How would I troubleshoot this issue further?
Thanks in advance,
Traiano
04-24-2017 12:14 AM
Any response yet? Surely this can't be a difficult issue to resolve?
04-24-2017 12:18 AM
Hi
You said : (i've also disabled SIM on the agent side): meaning the SIM enabled is set to false in the controller-info.xml right?
What's your controller version?
Have you checked the license screen? Have you reached any limit in term of license tokens?
If you want to get proper attention, maybe you should open a ticket to our support on the portal.
JB
04-25-2017 12:00 AM
Hi
Correct. Here is the specific line: <sim-enabled>false</sim-enabled>
As mentioned before, version is: AppDynamics Version 4.3.0.3, build 147
Attached screenshot of licensing output.
If it's necessary to run this through support, ok, I'll do that. I thought community support would be sufficient to resolve this kind of problem.
thanks,
Traiano
04-25-2017 12:20 AM
... Sorry I've just connected the dot..
You need to just put the account name, not the global account name in the controller-info.xml file. There's a recent identified bug on this.
Let me know
JB
04-25-2017 12:23 AM
Hi
Thanks for the response!
I know how to find the global account name, but where exactly do I find the "account name"? (apologies, appdynamics newbie here!)
Thanks in advance,
Traiano
04-25-2017 12:44 AM
Ok, this seems to work. There are other issues now, but I'll report them through the support portal.
04-25-2017 01:10 AM
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form