I have just installed the pro trial on my sever and the agent is not reporting. I see a red dot under "App Agent Status". In the logs on the server I see the folloing
[AD Thread Pool-Global0] 31 Mar 2014 22:04:41,272 ERROR ConfigurationChannel - Fatal transport error: Connection reset
[AD Thread Pool-Global0] 31 Mar 2014 22:04:41,272 WARN ConfigurationChannel - Invalid response for configuration request from controller/could not connect to controller. Msg : Fatal transport error: Connection reset
[AD Thread Pool-Global0] 31 Mar 2014 22:04:41,272 WARN ConfigurationChannel - Invalid response for configuration request from controller/could not connect to controller. Msg : Fatal transport error: Connection reset
[AD Thread-Metric Reporter0] 31 Mar 2014 22:05:29,963 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global1] 31 Mar 2014 22:05:41,398 INFO XMLConfigManager - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter0] 31 Mar 2014 22:06:29,963 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global0] 31 Mar 2014 22:06:50,942 INFO ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled
[AD Thread-Metric Reporter0] 31 Mar 2014 22:07:29,963 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread-Metric Reporter0] 31 Mar 2014 22:08:29,963 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread-Metric Reporter0] 31 Mar 2014 22:09:29,963 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
I also see this at the start of tomcat.
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [STG]
[INFO]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[INFO]: AgentInstallManager - Agent runtime directory set to [/home/mhiggins/appdynamics]
[INFO]: AgentInstallManager - Agent node directory set to [STG]
[WARN]: AgentInstallManager - Invalid Edition [Java Agent]. Keeping current edition [STANDARD]
[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.8.0.0 GA #2014-03-28_20-02-12 rccf93f47227e735b90c44a389eb2c7c2a203d082 8-3.8.0.next]
[INFO]: JavaAgent - Running IBM Java Agent [No]
[INFO]: JavaAgent - Java Agent Directory [/home/mhiggins/appdynamics]
Agent Logging Directory [/home/mhiggins/appdynamics/logs/STG]
Running obfuscated agent
Registered app server agent with Node ID[109679] Component ID[62862] Application ID [2007]
Started AppDynamics Java Agent Successfully.
Attached is the log file and the server config .
Hi Matt,
We see the following errors in agent logs,
===============================================
[AD Thread-Metric Reporter0] 31 Mar 2014 21:18:31,305 WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
..
[Thread-0] 31 Mar 2014 19:56:48,169 WARN ConfigurationChannel - ResponseReadException creating Response Wrapper [xb], : com.singularity.ee.rest.c: Error in controller in processing binary request AppAgent Config Data - java.lang.reflect.InvocationTargetException
[Thread-0] 31 Mar 2014 22:22:51,961 WARN ConfigurationChannel - ResponseReadException creating Response Wrapper [xb], : com.singularity.ee.rest.c: Error in controller in processing binary request AppAgent Config Data - java.lang.reflect.InvocationTargetException
..
[AD Thread Pool-Global1] 31 Mar 2014 22:25:52,121 WARN ConfigurationChannel - ResponseReadException creating Response Wrapper [xb], : com.singularity.ee.rest.c: Error in controller in processing binary request AppAgent Config Data - java.lang.reflect.InvocationTargetException
================================================
- also we see that you are using agent version 3.8.x as per agent logs:
[Thread-0] 31 Mar 2014 22:22:48,765 INFO JavaAgent - Using Java Agent Version [Server Agent v3.8.0.0 GA #2014-03-28_20-02-12 rccf93f47227e735b90c44a389eb2c7c2a203d082 8-3.8.0.next]
Can you please take a backup of /home/mhiggins/appdynamics directory and remove the contents and files under current agent directory and please download 3.7.15 agent from our download site http://download.appdynamics.com/onpremise/public/archives/3.7.15/AppServerAgent.zip and install 3.7.15 agent and provide the controller host/port and account name and access key details in addition to app/tier/node details and restart tomcat and see how it goes?
Please be sure that 3.8.x agent will not work with 3.7.15 controller version , as we your saas controller is 3.7.15 controller version. Please keep us posted how it goes after executing suggested changes.
Regards,
Arun
Thanks its working but here are a few things you might want to take a look at.
The version of the agent was from the getting started popup that is displayed when you first log into the account. Also the link you sent me I did not have permission to acces but I was able to find older versions of the agent by poking around the docs.
-Matt
Hi Matt,
Thanks for the note, yes your observation is right and this issue is already been escalated internally, we request you to make sure you are using agent version is not higher than the major version of controller say 3.7.x agent is compatable with 3.7.x+1 but not 3.8.x hope that informaiton helps.
Regards,
Arun
Hi Matt,
We would like to inform that the issue in download appropriate agent version is now fixed.
Regards,
Arun