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

cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy fail with python agent

Proxy fail with python agent

Hi,

 

I'm new to Appdynamics and I'm having error messages coming up regarding the proxy when using a python agent, I would appreciate any help to resolve this issue. 

 

If I follow the steps on the documentation and just create a /etc/appdynamics.cfg file :

 

[agent]

app = Test App

tier = Test Tier

node = node 0adb

 

[controller]

host = XXXX.saas.appdynamics.com

port = 443

ssl = (on)

account = XXX

accesskey = XXX



I get this error:



19:21:00,008  WARN [AD Thread-Metric Reporter0] MetricHandler - Metric Reporter Queue full. Dropping metrics.

19:21:20,171  INFO [AD Thread Pool-Global1] ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled

19:21:23,040  INFO [AD Thread Pool-Global1] ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:4416, Name:appdynamics.ip.addresses, Value:fe80:0:0:0:d453:dc4:33ad:b620%enp0s3,192.168.1.15]

19:21:23,040  INFO [AD Thread Pool-Global1] ConfigurationChannel - Sending Registration request with: Application Name [Test App], Tier Name [Test Tier], Node Name [node 0adb], Host Name [ChrisUbuntu-VM] Node Unique Local ID [node 0adb], Version [Python Agent v20.3.0.0 (proxy v4.5.16.28134, agent-api v4.3.5.0)]

19:21:23,559 ERROR [AD Thread Pool-Global1] ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]: org.apache.http.NoHttpResponseException: XXXX.saas.appdynamics.com:443 failed to respond

19:21:23,559  WARN [AD Thread Pool-Global1] ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [XXX.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]

19:22:00,008  WARN [AD Thread-Metric Reporter0] MetricHandler - Metric Reporter Queue full. Dropping metrics.

19:22:19,066  WARN [AD Thread Pool-Global1] EventGenerationService - The retention queue is at full capacity [5]. Dropping events for timeslice [Sun Apr 05 19:17:00 AEST 2020] to accomodate events for timeslice [Sun Apr 05 19:22:00 AEST 2020]





If I edit the controller-info.xml in /usr/local/lib/python3.6/dist-packages/appdynamics_bindeps/proxy/conf/controller-info.xml

 

With:

<controller-host>EDITED.saas.appdynamics.com</controller-host>

<controller-port>443</controller-port>

<application-name>Test App</application-name>

<tier-name>Test Tier</tier-name>

<node-name>node 0adb</node-name>

 <account-name>EDITED</account-name>

<account-access-key>EDITED</account-access-key>

   <use-ssl-client-auth>true</use-ssl-client-auth>



Then I get these errors: (log file /tmp/appd/logs/proxyCore.2020_04_05__20_12_05.0.log )

 

[Thread-1] 05 Apr 2020 20:12:41,174  INFO com.singularity.proxyControl.ProxyMultiNodeManager - Creating new node in proxy for node appName:Test App tierName:Test Tier nodeName:node 0adb

[Thread-1] 05 Apr 2020 20:12:41,175  INFO com.singularity.proxyControl.ProxyMultiNodeManager - Comm address for the start node request: [app.name=Test App,tier.name=Test Tier,node.name=node 0adb,controller.host.name=XXXXX.saas.appdynamics.com,account.name=XXXX,account.key=XXXX,controller.port=443] is: /tmp/appd/run/comm/proxy-7826785417410579370/n15

[AD Thread Pool-ProxyControlReq0] 05 Apr 2020 20:12:41,379  INFO com.singularity.proxyControl.ProxyMultiNodeManager - Removed lock for start node request for key [app.name=Test App1,tier.name=Test Tier1,node.name=node 0adb,controller.host.name=XXX.saas.appdynamics.com,account.name=XXX,account.key=01sbc6q69823,controller.port=443]

[AD Thread Pool-ProxyControlReq0] 05 Apr 2020 20:12:41,381  INFO com.singularity.proxyControl.ProxyMultiNodeManager - Proxy for node [app.name=Test App,tier.name=Test Tier,node.name=node 0adb,controller.host.name=XXXX.saas.appdynamics.com,account.name=XXX,account.key=XXXX,controller.port=443] has been started

[Thread-1] 05 Apr 2020 20:12:42,396 ERROR com.singularity.proxyControl.ProxyMultiNodeManager - Error while starting a new proxy node

java.lang.NullPointerException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at com.appdynamics.ee.agent.proxy.bootstrap.multiagent.ProxyMultiNodeManager.startProxy(ProxyMultiNodeManager.java:190)

        at com.appdynamics.ee.agent.proxy.bootstrap.ZeroMQControlServer$ReqHandler.run(ZeroMQControlServer.java:312)

        at java.lang.Thread.run(Thread.java:748)

[Thread-1] 05 Apr 2020 20:12:42,397 ERROR com.singularity.proxyControl.ProxyNode - Error while shutting down proxy node

java.lang.NullPointerException

        at com.appdynamics.ee.agent.proxy.bootstrap.multiagent.ProxyNode.shutdown(ProxyNode.java:152)

        at com.appdynamics.ee.agent.proxy.bootstrap.multiagent.ProxyMultiNodeManager.stopProxyNode(ProxyMultiNodeManager.java:222)

        at com.appdynamics.ee.agent.proxy.bootstrap.multiagent.ProxyMultiNodeManager.startProxy(ProxyMultiNodeManager.java:207)

        at com.appdynamics.ee.agent.proxy.bootstrap.ZeroMQControlServer$ReqHandler.run(ZeroMQControlServer.java:312)

        at java.lang.Thread.run(Thread.java:748)

Proxy fail with python agent
1 REPLY 1
AppDynamics Team

Re: Proxy fail with python agent

Hi Christopher,

 

Could you please change 

 

ssl = (on)

 

to

 

ssl = on

 

 in the /etc/appdynamics.cfg file, restart your application as well as the JAVA proxy process and verify if that helps resolve the connectivity issues? Please also revert all the changes you did in the controller-info.xml file.

 

Best Regards,

Piyush