topic Re: Could not connect to the controller/invalid response from controller in Splunk AppDynamics

Could not connect to the controller/invalid response from controller

CommunityUser — Mon, 16 Oct 2017 14:21:24 GMT

Hi
I installed Python Agent, and from the controller (Getting Started Wizard) it shows the agent is connected but the App agent status is not showing up and below is the message from logs and PFA of appd_logs in zip format.

16 Oct 2017 13:27:44,947 WARN com.singularity.CONFIG.ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [pitneybowesall.saas.appdynamics.com], port[443], exception [Connection back off limitation in effect: /controller/instance/0/applicationConfiguration]
[AD Thread Pool-Global1] 16 Oct 2017 13:27:44,947 ERROR com.singularity.CONFIG.ConfigurationChannel - Exception: NULL
[AD Thread-Metric Reporter1] 16 Oct 2017 13:28:16,885 WARN com.singularity.METRICS.MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [appdynamics.http.proxyPasswordFile]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [PTS_BASICAUTH_PASSWORD]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [SAAS_E2E_PASSWORD]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [HORIZON_BASICAUTH_PASSWORD]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [GPG_KEY]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [AWS_SECRET_KEY]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [APPD_ACCESS_KEY]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [SUMO_ACCESS_KEY]
[AD Thread Pool-Global0] 16 Oct 2017 13:28:44,948 INFO com.singularity.KernelProperties - Filtering data with key = [AWS_ACCESS_KEY_ID]
[AD Thread Pool-Global0]

Thanks in Advance

Regards,

Jai

^ Post edited by @Ryan.Paredez to remove the attached log files. Please do not attach or past log files into Community posts for security and privacy reasons.

Re: Could not connect to the controller/invalid response from controller

Piyush_Mundra — Mon, 16 Oct 2017 15:14:16 GMT

Hi Jai,

Could you please check the agent config file you have in the environment for the SSL setting. If it is set to

ssl = (on)

then please change it to

ssl = on

and restart the JAVA proxy followed by the Python application and see if this helps.

Best Regards,

Piyush

Re: Could not connect to the controller/invalid response from controller

CommunityUser — Wed, 08 Nov 2017 21:08:28 GMT

Hi Piyush,

Thanks for the reply.

the agent is connectd to controller but data is not coming in.

Pyagent is installed on a proxy server, is there a way to get data from proxy server to send to our saas controller?

Thanks,

Jai

Re: Could not connect to the controller/invalid response from controller

Piyush_Mundra — Thu, 09 Nov 2017 16:14:40 GMT

Hi Jai,

Is the server have a proxy setup for outbound requests, we can set them in the agent config so the agent would be able to send the metrics to the controller. Please have a look at https://docs.appdynamics.com/display/PRO42/Python+Agent+Settings#PythonAgentSettings-[controller:http-proxy] for details on the network proxy settings.

Best Regards,

Piyush

Re: Could not connect to the controller/invalid response from controller

CommunityUser — Fri, 27 Jul 2018 16:31:55 GMT

My issue was solved after bring node online on controller