AppD Archive

agent + controller connectivity error

CommunityUser
Splunk Employee
Splunk Employee

Hi,

this is my third post and you helps me good. Thank you.

Now I have issue with some jar program. As I sew in attached logs, there are some missmatch between agent and controller which is in SaaS. Can you find time and look attached logs? 

Thank you

0 Karma
1 Solution

Arun_Dasetty
Super Champion

Hi,

- We could access your saas account and paid139 host fine from our end ,but it looks the issue is from agent instance, please check if there are any proxy or firewall rules at your network end, in case of proxy we need to add below args before -javaagent and this change needs a restart, Hope that information helps:

-Dappdynamics.http.proxyHost= -Dappdynamics.http.proxyPort=

We can check from shell console on host "imb-web" to check connectivity: 

shell> telnet paid139.saas.appdynamics.com 443

shell> telnet JscBankofGeorgia.saas.appdynamics.com 443

[Thread-0] 06 Oct 2015 17:26:58,563 INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [imb-web]

[AD Thread Pool-Global1] 06 Oct 2015 17:28:00,461 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [paid139.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]
..[AD Thread Pool-Global1] 06 Oct 2015 17:28:00,461 ERROR ConfigurationChannel - Exception: Connect to paid139.saas.appdynamics.com:443 [paid139.saas.appdynamics.com/69.27.44.204] failed: Connection refused
org.apache.http.conn.HttpHostConnectException: Connect to paid139.saas.appdynamics.com:443 [paid139.saas.appdynamics.com/69.27.44.204] failed: Connection refused
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)

Regards,

Arun

View solution in original post

0 Karma

Arun_Dasetty
Super Champion

Hi,

- We could access your saas account and paid139 host fine from our end ,but it looks the issue is from agent instance, please check if there are any proxy or firewall rules at your network end, in case of proxy we need to add below args before -javaagent and this change needs a restart, Hope that information helps:

-Dappdynamics.http.proxyHost= -Dappdynamics.http.proxyPort=

We can check from shell console on host "imb-web" to check connectivity: 

shell> telnet paid139.saas.appdynamics.com 443

shell> telnet JscBankofGeorgia.saas.appdynamics.com 443

[Thread-0] 06 Oct 2015 17:26:58,563 INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [imb-web]

[AD Thread Pool-Global1] 06 Oct 2015 17:28:00,461 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [paid139.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]
..[AD Thread Pool-Global1] 06 Oct 2015 17:28:00,461 ERROR ConfigurationChannel - Exception: Connect to paid139.saas.appdynamics.com:443 [paid139.saas.appdynamics.com/69.27.44.204] failed: Connection refused
org.apache.http.conn.HttpHostConnectException: Connect to paid139.saas.appdynamics.com:443 [paid139.saas.appdynamics.com/69.27.44.204] failed: Connection refused
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thank you akumar. Thats it! 

0 Karma
Get Updates on the Splunk Community!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

New Release | Splunk Cloud Platform 10.1.2507

Hello Splunk Community!We are thrilled to announce the General Availability of Splunk Cloud Platform 10.1.2507 ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...