Controller (SaaS, On Premise)

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect to the controller

Producer

Unable to connect to the controller

We connect to Appdynamics to SaaS controller on port 80, I was able to send application data to Appdynamics earlier and it was working fine. Now I see below error in logs,  please advise.

 

^ Post edited by @Ryan.Paredez for security reasons. Please do not share or attach log files to community posts.

Unable to connect to the controller
15 REPLIES 15
AppDynamics Team

Re: Unable to connect to the controller

Hi Kiran,

 

Please let us know if there is any changes made on the controller side or the Agent side and then you started seeing this issue.

Could you please attach the complete agent log folder. Along with that provide the output of 

shell > curl -v https://<domain-name>.saas.appdynamics.com:80 or ping command output.

 

Thanks,

Yogesh



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

Re: Unable to connect to the controller

Hi Yogesh,



It was working fine earlier, it stopped working recently. Attached is the log files folder.



ping deloitteapm.saas.appdynamics.com



Pinging myzgj.x.incapdns.net [message redacted to protect privacy] with 32 bytes of data:

[message redacted to protect privacy]


Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 213ms, Maximum = 215ms, Average = 214ms


I am able to telnet to [message redacted to protect privacy] on port 80.


Highlighted
AppDynamics Team

Re: Unable to connect to the controller

Hi,

 

Could you please attach the agent log as we could see it is missing in your earlier post.

 

Thanks,

Atyuha



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

Re: Unable to connect to the controller

[Log file removed]

 

^ Post edited by @Ryan.Paredez for security reasons. Please do not share or attach log files to community posts.

Producer

Re: Unable to connect to the controller

Anybody know why the below error is coming? Is it the problem with the account? I am able to telnet the controller on port 80. The integration was working fine, now it stopped working.

 

Below is the error i am getting:

 

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6320, Name:appdynamics.ip.addresses, Value:192.168.0.102,fe80:0:0:0:d5cc:b070:55a2:d156%wlan0,fe80:0:0:0:ed86:cfba:bc2d:41eb%eth1,fe80:0:0:0:1001:79d6:4d90:20be%eth2,fe80:0:0:0:0:5efe:c0a8:66%net1,fe80:0:0:0:5068:8f02:14ce:39c5%wlan1,fe80:0:0:0:6966:e7e0:b37:6a81%eth6, Name:supportsDevMode, Value:true]

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [MyTier], Node Name [message redacted to protect privacy], Host Name [dell] Node Unique Local ID [Tomcat@dell:8005], Version [Server Agent v4.3.7.1 GA #15472 r666c888950068365d8a7d2ec64268aedb53d9b87 13534-4.3.7.next-analytics]

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [message redacted to protect privacy], port[80], exception [Connection back off limitation in effect: /controller/instance/0/applicationConfiguration]

[AD Thread Pool-Global0] 09 Mar 2018 08:50:38,351 ERROR ConfigurationChannel - Exception: NULL

[AD Thread-Metric Reporter1] 09 Mar 2018 08:51:04,358  WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6320, Name:appdynamics.ip.addresses, Value:192.168.0.102,fe80:0:0:0:d5cc:b070:55a2:d156%wlan0,fe80:0:0:0:ed86:cfba:bc2d:41eb%eth1,fe80:0:0:0:1001:79d6:4d90:20be%eth2,fe80:0:0:0:0:5efe:c0a8:66%net1,fe80:0:0:0:5068:8f02:14ce:39c5%wlan1,fe80:0:0:0:6966:e7e0:b37:6a81%eth6, Name:supportsDevMode, Value:true]

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [MyTier], Node Name [message redacted to protect privacy], Host Name [dell] Node Unique Local ID [Tomcat@dell:8005], Version [Server Agent v4.3.7.1 GA #15472 r666c888950068365d8a7d2ec64268aedb53d9b87 13534-4.3.7.next-analytics]

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [message redacted to protect privacy], port[80], exception [Connection back off limitation in effect: /controller/instance/0/applicationConfiguration]

[AD Thread Pool-Global0] 09 Mar 2018 08:51:38,360 ERROR ConfigurationChannel - Exception: NULL

[AD Thread-Metric Reporter1] 09 Mar 2018 08:52:04,361  WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.

[AD Thread Pool-Global0] 09 Mar 2018 08:54:01,546  INFO ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546  INFO KernelProperties - Filtering data with key = [jdk.tls.ephemeralDHKeySize]

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6320, Name:appdynamics.ip.addresses, Value:192.168.0.102,fe80:0:0:0:d5cc:b070:55a2:d156%wlan0,fe80:0:0:0:ed86:cfba:bc2d:41eb%eth1,fe80:0:0:0:1001:79d6:4d90:20be%eth2,fe80:0:0:0:0:5efe:c0a8:66%net1,fe80:0:0:0:5068:8f02:14ce:39c5%wlan1,fe80:0:0:0:6966:e7e0:b37:6a81%eth6, Name:supportsDevMode, Value:true]

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [MyTier], Node Name [Tomcat@dell:8005], Host Name [dell] Node Unique Local ID [Tomcat@dell:8005], Version [Server Agent v4.3.7.1 GA #15472 r666c888950068365d8a7d2ec64268aedb53d9b87 13534-4.3.7.next-analytics]

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [message redacted to protect privacy], port[80], exception [Connection back off limitation in effect: /controller/instance/0/applicationConfiguration]

[AD Thread Pool-Global1] 09 Mar 2018 08:54:01,546 ERROR ConfigurationChannel - Exception: NULL

[AD Thread-Metric Reporter0] 09 Mar 2018 08:54:02,964  WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.

Re: Unable to connect to the controller

I'm currently having a similar issue

Discoverer

Re: Unable to connect to the controller

Hi, everybody!

 

Did you solve the issue?

I am facing the same error in one of ours servers:

 

2018-05-15 08:46:26.9604 5600 AppDynamics.Coordinator 1 11 Info CoordinatorService Stopped Machine Agent.
2018-05-15 08:46:28.3175 5600 AppDynamics.Coordinator 1 8 Info CoordinatorService Starting communicator...
2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator starting named pipe server
2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator named pipe = \\.\pipe\AppDynamicsAgentIPC
2018-05-15 08:51:26.0453 5600 AppDynamics.Coordinator 1 17 Info ControllerTimeSkewHandler Controller Time Skew Handler Run Aborted - Skew Check is Disabled

AppDynamics Team

Re: Unable to connect to the controller

Anybody? I currently also face this trouble of "Connection back off limitation in effect".

Adventurer

Re: Unable to connect to the controller

I am also facing the same: 

 org.apache.http.NoHttpResponseException: blah.saas.appdynamics.com:443 failed to respond