Infrastructure (Server, Network, Database)

cancel
Showing results for 
Search instead for 
Did you mean: 

AppDynamic agent error failed to respond

New Member

AppDynamic agent error failed to respond

Hi
I downloaded AppDynamic Pro trial for 15 days and use as saas.
After I installed agent and start Tomcat I got error message
 
[AD Thread Pool-Global0] 24 Nov 2014 15:18:26,375 ERROR ConfigurationChannel - Fatal transport error: The server paid51.saas.appdynamics.com failed to respond
[AD Thread Pool-Global0] 24 Nov 2014 15:18:26,376 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [paid51.saas.appdynamics.com], port[443], exception [Fatal transport error: The server paid51.saas.appdynamics.com failed to respond]
[AD Thread Pool-Global0] 24 Nov 2014 15:18:26,376 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - org.apache.commons.httpclient.NoHttpResponseException,2147483647]
[AD Thread Pool-Global0] 24 Nov 2014 15:18:26,376 WARN AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
[AD Thread Pool-Global0] 24 Nov 2014 15:18:26,376 ERROR ConfigurationChannel - Exception: The server paid51.saas.appdynamics.com failed to respond
org.apache.commons.httpclient.NoHttpResponseException: The server paid51.saas.appdynamics.com failed to respond
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1976)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.singularity.ee.util.httpclient.j.a(j.java:212)
at com.singularity.ee.rest.h.G(h.java:426)
at com.singularity.ee.rest.h.F(h.java:371)
at com.singularity.ee.rest.controller.request.vb.F(vb.java:124)
at com.singularity.ee.rest.controller.request.wb.a(wb.java:35)
at com.singularity.ee.agent.appagent.kernel.config.xml.l.a(l.java:1304)
at com.singularity.ee.agent.appagent.kernel.config.xml.l.a(l.java:77)
at com.singularity.ee.agent.appagent.kernel.config.xml.s.a(s.java:561)
at com.singularity.ee.agent.appagent.kernel.config.xml.l.a(l.java:392)
at com.singularity.ee.agent.appagent.kernel.config.xml.db.run(db.java:660)
at com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at com.singularity.ee.util.javaspecific.scheduler.y.e(y.java:315)
at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:150)
at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:123)
at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:208)
at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:238)
at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:683)
at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:715)
at java.lang.Thread.run(Thread.java:745)
 
And also cannot ping to host paid51.saas.appdynamics.com
I attached file controller-info.xml in this post.
Please advise me.
Thanks.

AppDynamic agent error failed to respond
8 REPLIES 8
New Member

Re: AppDynamic agent error failed to respond

why I can't attached file to this post

AppDynamics Team

Re: AppDynamic agent error failed to respond

Hi,

 

We see ping is disabled to saas host and that could be reason for ping request failed.  Can you check whether from agent instance controller could reach fine using telnet command:

 

shell> telnet paid51.saas.appdynamics.com 443

shell> telnet paid51.saas.appdynamics.com 80

 

Also please confirm whether you have provided account-name and access-key details with ssl-enabed xml element set to true in <agent_dir>/conf/controller-info.xml , Can you try attach all logs in zip format for logs under <agent_dir>/logs path to debug further if issue persists?

 

We suspect that the file extension might you try to attach not be supported and that could be the reason, please do zip and attach logs to assist you further.

 

Regards,

Arun



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
New Member

Re: AppDynamic agent error failed to respond

Hi Arun

Thanks for your reply.

I can telnet to paid51.saas.appdynamics.com 443.

I have provided account-name and access key but without ssl-enable.

 

I have attached log.zip in this post

Thanks.

AppDynamics Team

Re: AppDynamic agent error failed to respond

Hi,

 

Can you quickly set the following element to true in controller-info.xml at /clickclass/jvmagent/conf path and restart jvm after saving changes and see how it goes:

<controller-ssl-enabled>false</controller-ssl-enabled>

 

Regards,

Arun



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Highlighted
New Member

Re: AppDynamic agent error failed to respond

Do you mean if I use port 443, then I have to set controller-ssl-enabled to true?

What if I change port to 80 so no need to change controller-ssl-enabled to true?

New Member

Re: AppDynamic agent error failed to respond

Dear Arun

I had changed port to 80 and now I can see information from agent in controller.

 

Thanks so much for your support.

Have a nice day!!

Tags (1)
AppDynamics Team

Re: AppDynamic agent error failed to respond

Hi,

 

Glad to hear that news from you, To answer your queries, yes 443 is https port and ssl-enabled should be set to true and 80 is http port and ssl-enabled flag should be false.

 

Regards,

Arun



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Explorer

Re: AppDynamic agent error failed to respond

Hi, i'm getting the following error when i start:

It says unknown host. Can u let me know the IP address of my host : hsbc1.saas.appdynamics.com

[Thread-2] 06 Dec 2016 13:19:54,499  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6740, Name:appdynamics.ip.addresses, Value:136.55.182.37, Name:supportsDevMode, Value:true]
[Thread-2] 06 Dec 2016 13:19:54,499  INFO ConfigurationChannel - Sending Registration request with: Application Name [DemoGCM], Tier Name [demo], Node Name [demo], Host Name [A35677DYD5JRKVH] Node Unique Local ID [demo], Version [Server Agent v4.2.7.1 GA #13005 rc04adaef4741dbb8f2e7c206bdb2a6614046798a 11-4.2.7.next-analytics]
[Thread-2] 06 Dec 2016 13:19:54,747 ERROR ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]: java.net.UnknownHostException: hsbc1.saas.appdynamics.com: hsbc1.saas.appdynamics.com
[Thread-2] 06 Dec 2016 13:19:54,747  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [hsbc1.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]
[Thread-2] 06 Dec 2016 13:19:54,751  WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - java.net.UnknownHostException,2147483647]
[Thread-2] 06 Dec 2016 13:19:54,751  WARN AgentErrorProcessor - 4 instance(s) remaining before error log is silenced
[Thread-2] 06 Dec 2016 13:19:54,752 ERROR ConfigurationChannel - Exception: hsbc1.saas.appdynamics.com: hsbc1.saas.appdynamics.com
java.net.UnknownHostException: hsbc1.saas.appdynamics.com: hsbc1.saas.appdynamics.com
 at java.net.InetAddress.getAllByName0(InetAddress.java:1269)
 at java.net.InetAddress.getAllByName(InetAddress.java:1196)
 at java.net.InetAddress.getAllByName(InetAddress.java:1118)
 at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
 at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:102)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
 at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
 at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
 at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
 at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
 at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
 at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
 at com.singularity.ee.util.httpclient.l.a(l.java:275)
 at com.singularity.ee.util.httpclient.l.a(l.java:190)
 at com.singularity.ee.rest.d.y(d.java:387)
 at com.singularity.ee.rest.d.x(d.java:340)
 at com.singularity.ee.rest.controller.request.nb.x(nb.java:98)
 at com.singularity.ee.rest.controller.request.ob.a(ob.java:35)
 at com.singularity.ee.agent.appagent.kernel.config.xml.i.a(i.java:1280)
 at com.singularity.ee.agent.appagent.kernel.config.xml.i.a(i.java:108)
 at com.singularity.ee.agent.appagent.kernel.config.xml.p.a(p.java:617)
 at com.singularity.ee.agent.appagent.kernel.config.xml.i.a(i.java:420)
 at com.singularity.ee.agent.appagent.kernel.config.xml.ab.run(ab.java:662)
 at com.singularity.ee.agent.appagent.kernel.config.xml.d.initialize(d.java:273)
 at com.singularity.ee.agent.appagent.kernel.l.start(l.java:120)
 at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:428)
 at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:242)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 at com.singularity.ee.agent.appagent.AgentEntryPoint$1.run(AgentEntryPoint.java:481)
[Thread-2] 06 Dec 2016 13:19:54,755  INFO XMLConfigManager - Agent will poll for new configuration from controller every [60] seconds

 

 

 

 

[Thread-2] 06 Dec 2016 13:19:53,979  INFO com.singularity.dynamicservice.DynamicServiceManager - Scheduling DynamicServiceManager at interval of 30 seconds
[AD Thread Pool-Global1] 06 Dec 2016 13:20:23,980  INFO com.singularity.dynamicservice.DynamicServiceManager - Using services directories [C:\appd-agent\ver4.2.7.1\external-services, C:\appd-agent\ver4.2.7.1\external-services\demo]
[AD Thread Pool-Global1] 06 Dec 2016 13:20:23,980  INFO com.singularity.dynamicservice.DynamicServiceManager - Mbean registration failed or not ready
[AD Thread Pool-Global0] 06 Dec 2016 13:21:54,002  INFO com.singularity.dynamicservice.DynamicServiceMBeanManager - MBean AppDynamics:cell=A35677DYD5JRKVHNode01Cell,type=DynamicServiceManager,node=A35677DYD5JRKVHNode01,process=server1 is registered
[AD Thread Pool-Global0] 06 Dec 2016 13:21:54,514 ERROR com.singularity.dynamicservice.DynamicServiceMBeanManager - Exception: javax.management.RuntimeOperationsException: Exception occured trying to invoke the setter on the MBean trying to set objectName attribute from ObjectName AppDynamics:cell=A35677DYD5JRKVHNode01Cell,type=DynamicServiceManager,node=A35677DYD5JRKVHNode01,process=server1
javax.management.RuntimeOperationsException: Exception occured trying to invoke the setter on the MBean
 at com.ibm.ws.management.PlatformMBeanServer.setAttribute(PlatformMBeanServer.java:716)
 at com.singularity.ee.agent.appagent.kernel.fb.b(fb.java:207)
 at com.singularity.ee.agent.appagent.kernel.fb.invoke(fb.java:142)
 at $Proxy48.setObjectName(Unknown Source)
 at com.singularity.ee.agent.appagent.kernel.eb.a(eb.java:289)
 at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager._registerMBean(DynamicServiceManager.java:960)
 at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.registerMBean(DynamicServiceManager.java:939)
 at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.registerMBean(DynamicServiceManager.java:236)
 at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.pollForNewServices(DynamicServiceManager.java:322)
 at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.run(DynamicServiceManager.java:280)
 at com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:122)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452)
 at com.singularity.ee.util.javaspecific.scheduler.z.e(z.java:335)
 at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:152)
 at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:119)
 at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:206)
 at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:236)
 at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694)
 at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726)
 at java.lang.Thread.run(Thread.java:772)
Caused by: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the setObjectName operation on DynamicServiceManager MBean because of insufficient or empty credentials.
 at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2382)
 at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2189)
 at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2083)
 at com.ibm.ws.management.AdminServiceImpl.setAttribute(AdminServiceImpl.java:1056)
 at com.ibm.ws.management.PlatformMBeanServer.setAttribute(PlatformMBeanServer.java:713)