Dynamic Languages (Node.JS, Python, PHP, C/C++, Webserver Agent)

cancel
Showing results for 
Search instead for 
Did you mean: 

saas.appdynamics.com failed to respond

SOLVED
Highlighted
Creator

Hi,

 

I use pyagent to run....and I get the following error.

 

 

10:50:33,311 WARN [AD Thread Pool-Global1] AgentErrorProcessor - 3 instance(s) remaining before error log is silenced
10:50:33,311 ERROR [AD Thread Pool-Global1] ConfigurationChannel - Exception: earhart2020040113170721.saas.appdynamics.com:443 failed to respond
org.apache.http.NoHttpResponseException: earhart2020040113170721.saas.appdynamics.com:443 failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) ~[httpcore-4.4.9.jar:4.4.9]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[httpclient-4.5.4.jar:4.5.4]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) ~[httpclient-4.5.4.jar:4.5.4]
at com.singularity.ee.util.httpclient.SimpleHttpClientWrapper.executeHttpOperation(SimpleHttpClientWrapper.java:289) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.httpclient.SimpleHttpClientWrapper.executeHttpOperation(SimpleHttpClientWrapper.java:204) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.RESTRequest.sendRequestTracked(RESTRequest.java:384) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.RESTRequest.sendRequest(RESTRequest.java:337) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.controller.request.AControllerRequest.sendRequest(AControllerRequest.java:130) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.sendRequest(ABinaryControllerRequest.java:36) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.ConfigurationChannel.registerApplicationServer(ConfigurationChannel.java:1480) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.ConfigurationChannel.access$100(ConfigurationChannel.java:122) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.ConfigurationChannel$UnregisteredConfigurationState.nextTransition(ConfigurationChannel.java:742) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.ConfigurationChannel.refreshConfiguration(ConfigurationChannel.java:521) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.agent.appagent.kernel.config.xml.XMLConfigManager$AgentConfigurationRefreshTask.run(XMLConfigManager.java:649) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_212]
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726) ~[proxy.jar:Proxy v${python-agent-version} GA SHA-1: DEV-BUILD Date ${TODAY}]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]

 

 but i can access appdynamics

 

telnet earhart2020040113170721.saas.appdynamics.com 443
Trying 34.208.167.103...
Connected to pdx-p-con-1501.saas.appdynamics.com.
Escape character is '^]'

 

Tags (1)
saas.appdynamics.com failed to respond
10 REPLIES 10
Highlighted
AppDynamics Team

https://docs.appdynamics.com/display/PRO45/Install+the+Python+Agent#InstallthePythonAgent-Configuret...

 

Please reference the link above, can you confirm that SSL is enabled (on) in the config?

 

And please double check the account and accesskey fields match what shows in your SaaS controller, Gear Cog Icon (top right) > License > Account.

 

Are you using a proxy on this machine? 




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

1. My config copy from GETTING_STARTED_PYTHON, after double check the account and pass is correct.

2. No, My server don't need proxy to access internet. @Philip.Rogers 

3. My app run in python3.8 in docker, is that root cause, the doc say it  just support 3.7?

 

My config seems like it

 

 

[agent]
app = fake
tier =fake
node = nodefake

[controller]
host =fake.saas.appdynamics.com
port = 443
ssl = (on)
account =fake
accesskey =fake

 

 

From the log, it seems the XML config has an issue, but I don't know where to config 

 

 

/tmp/appd/logs/node c45e# grep account *.log
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,845  INFO com.singularity.XMLConfigManager - Default Agent Account Info Resolver found system property [appdynamics.agent.accountName] for account name [earhart2020040113170721]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,845  INFO com.singularity.XMLConfigManager - Default Agent Account Info Resolver found system property [appdynamics.agent.accountAccessKey] for account access key [****]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,861  INFO com.singularity.XMLConfigManager - XML Agent Account Info Resolver did not find account name. Using default account name [customer1]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,861  WARN com.singularity.XMLConfigManager - XML Agent Account Info Resolver did not find account access key.

 

 

 

root@xxxx:/tmp/appd/logs/node c45e# lsof agent.2020_04_03__04_14_27.log
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
java    4622 root   63u   REG   0,45   165373 411888 agent.2020_04_03__04_14_27.log
root@xxxx:/tmp/appd/logs/node c45e# ps -ef|grep 4622
root      4622  4621  2 04:12 pts/5    00:00:20 /usr/local/lib/python3.8/site-packages/appdynamics_proxysupport/bin/java -server -Xmx300m -Xms50m -classpath /usr/local/lib/python3.8/site-packages/appdynamics_bindeps/proxy/conf/logging:/usr/local/lib/python3.8/site-packages/appdynamics_bindeps/proxy/lib/*:/usr/local/lib/python3.8/site-packages/appdynamics_bindeps/proxy/lib/tp/*:/usr/local/lib/python3.8/site-packages/appdynamics_bindeps/proxy/* -Djava.library.path=/usr/local/lib/python3.8/site-packages/appdynamics_bindeps/proxy/lib/tp -Dappdynamics.agent.logs.dir=/tmp/appd/logs -Dcomm=/tmp/appd/run/comm -DagentType=PYTHON_APP_AGENT -Dappdynamics.agent.runtime.dir=/tmp/appd/run -Dlog4j.ignoreTCL=true -XX:MaxPermSize=120m -XX:-UseGCOverheadLimit com.appdynamics.ee.agent.proxy.bootstrap.ProxyControlEntryPoint

 

 

Highlighted
AppDynamics Team

Hi @Bin.Hu 

 

Were you able to make any progress on your end?

 

It looks like the python agent may not be pointing to the proper configuration file, since the log file is complaining about not finding specific values and using defaults. Your provided configuration looks correct. 




Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Highlighted
Creator
/tmp/appd/logs/node c45e# grep account *.log
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,845  INFO com.singularity.XMLConfigManager - Default Agent Account Info Resolver found system property [appdynamics.agent.accountName] for account name [earhart2020040113170721]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,845  INFO com.singularity.XMLConfigManager - Default Agent Account Info Resolver found system property [appdynamics.agent.accountAccessKey] for account access key [****]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,861  INFO com.singularity.XMLConfigManager - XML Agent Account Info Resolver did not find account name. Using default account name [customer1]
agent.2020_04_03__04_14_27.log:[AD Thread Pool-ProxyControlReq0] 03 Apr 2020 04:14:27,861  WARN com.singularity.XMLConfigManager - XML Agent Account Info Resolver did not find account access key.

do u feel strange about above log?

  first line, it report account name  earhart,

  third line, it report account name customer1.

there is only one config to set account name,  is there a bug?

Highlighted
AppDynamics Team

Hi @Bin.Hu 

 

Is this a paid license or a trial license?

 

The best next step (if a paid license) is to contact support directly via the support portal (https://www.appdynamics.com/support) so one of our Python experts can point you in the correct direction. 

 

If this is a trial license, please use our Contact Us page (https://www.appdynamics.com/company/contact-us/) to get in touch with sales. They can arrange for support to get involved and help solve the issues you're running into.




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

I think there's an error in the documentation and wizard. I had this same error, and when I changed this (which the documentation shows and the wizard generates):

 

ssl = (on)
 
to this:
 
ssl = true
 
The problem was resolved, and my Django app connects to AppDynamics. That is, you should use true instead of (on).
 
Highlighted
Community Manager

Hi @Jim.Cushing,

 

Thanks for sharing that insight. I have created a ticket with the Docs team to have that piece of reviewed.

 


Thanks,
Ryan, 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.
Highlighted
Community Manager

Hi @Jim.Cushing ,

 

I wanted to followup to let you know the Docs page: (https://docs.appdynamics.com/display/PRO45/Install+the+Python+Agent#InstallthePythonAgent-Configuret...has been edited and corrected based on your comments. 


Thanks,
Ryan, 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.
Highlighted
Creator

Thanks for updating that. Through some experimentation, I found that values of "true" or "on" both work, but a value of "(on)" (with parentheses) does not work. 

 

The Getting Started Wizard, however, still generates an invalid configuration. For example:

 

 

[agent]
app = my-app-name
tier = my-tier-name
node = node abcd

[controller]
host = myaccount.saas.appdynamics.com
port = 443
ssl = (on)
account = myaccount
accesskey = myaccesskey

 

 

To see this:

 

  1. Creat a new application using Getting Started Wizard
  2. Select Python as the application type
  3. Verify that "Use SSL" is checked
  4. Fill in values for application and tier
  5. Click continue
  6. Scroll to "Install the App Agent" and examine the configuration file. Observe that is has "ssl = (on)" which should be either "ssl = on" or "ssl = true".