AppD Archive

I download and configure on Jboss, I see the error: UnknownHostException: paid29.saas.appdynamic.com

CommunityUser
Splunk Employee
Splunk Employee

Hi AppDynamics Operations Team.

 
I unzip and configured the script for the app server, in my case Jboss, but I don't see the monitoring for the application in my dashboard. In the log i see the next error:
 
[AD Thread Pool-Global1] 12 Jun 2013 00:23:23,031  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [PolicyCenter], Node Name [PolicyCenter], Host Name [PSGDWSYT0100.ppstst.com.pe] Node Unique Local ID [PolicyCenter], Version [Server Agent v3.7.1.1 GA #2013-05-30_14-30-03 rfae6a263dfb6946da5ad0cfe1ddcb77ef384e43b 5]
[AD Thread Pool-Global1] 12 Jun 2013 00:23:33,042 ERROR ConfigurationChannel - Fatal transport error: paid29.saas.appdynamics.com
[AD Thread Pool-Global1] 12 Jun 2013 00:23:33,042  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [paid29.saas.appdynamics.com], port[443], exception [Fatal transport error: paid29.saas.appdynamics.com]
[AD Thread Pool-Global1] 12 Jun 2013 00:23:33,042  WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - java.net.UnknownHostException,2147483647]
[AD Thread Pool-Global1] 12 Jun 2013 00:23:33,042  WARN AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
[AD Thread Pool-Global1] 12 Jun 2013 00:23:33,042 ERROR ConfigurationChannel - Exception: paid29.saas.appdynamics.com
java.net.UnknownHostException: paid29.saas.appdynamics.com
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:529)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
        at com.singularity.ee.rest.controller.request.d.createSocket(d.java:189)
        at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
        at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
        at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
        at com.singularity.ee.util.httpclient.j.a(j.java:189)
        at com.singularity.ee.rest.h.G(h.java:421)
        at com.singularity.ee.rest.h.F(h.java:366)
        at com.singularity.ee.rest.controller.request.rb.F(rb.java:114)
 
[AD Thread Pool-Global0] 12 Jun 2013 00:23:41,992  WARN EventHandler - Failed to send events for timeslice [Wed Jun 12 00:19:00 PET 2013]. The agent will try to resend the events again during the next 1 min window.
[AD Thread Pool-Global1] 12 Jun 2013 00:23:42,455  INFO ControllerTimeSkewHandler - Controller Time Skew Handler Run Aborted - Skew Check is Disabled
[AD Thread Pool-Global1] 12 Jun 2013 00:23:53,359  INFO DynamicRulesManager - The config directory /opt/AppDynamicsPro/AppServerAgent/conf/PolicyCenter is not initialized, not writing /opt/AppDynamicsPro/AppServerAgent/conf/PolicyCenter/bcirules.xml
[AD Thread-Metric Reporter0] 12 Jun 2013 00:24:21,968  WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global0] 12 Jun 2013 00:24:33,047  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6627, Name:appdynamics.ip.addresses, Value:172.30.19.46]
[AD Thread Pool-Global0] 12 Jun 2013 00:24:33,047  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [PolicyCenter], Node Name [PolicyCenter], Host Name [PSGDWSYT0100.ppstst.com.pe] Node Unique Local ID [PolicyCenter], Version [Server Agent v3.7.1.1 GA #2013-05-30_14-30-03 rfae6a263dfb6946da5ad0cfe1ddcb77ef384e43b 5]
[AD Thread Pool-Global1] 12 Jun 2013 00:24:41,993  WARN EventHandler - The retention queue is at full capacity [5]. Dropping events for timeslice [Wed Jun 12 00:19:00 PET 2013] to accomodate events for timeslice [Wed Jun 12 00:24:00 PET 2013]
[AD Thread Pool-Global0] 12 Jun 2013 00:24:43,053 ERROR ConfigurationChannel - Fatal transport error: paid29.saas.appdynamics.com
[AD Thread Pool-Global0] 12 Jun 2013 00:24:43,054  WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [paid29.saas.appdynamics.com], port[443], exception [Fatal transport error: paid29.saas.appdynamics.com]
[AD Thread-Metric Reporter0] 12 Jun 2013 00:25:21,968  WARN MetricHandler - Metric Reporter Queue full. Dropping metrics.
[AD Thread Pool-Global1] 12 Jun 2013 00:25:43,055  INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:6627, Name:appdynamics.ip.addresses, Value:172.30.19.46]
[AD Thread Pool-Global1] 12 Jun 2013 00:25:43,056  INFO ConfigurationChannel - Sending Registration request with: Application Name [MyApp], Tier Name [PolicyCenter], Node Name [PolicyCenter], Host Name [PSGDWSYT0100.ppstst.com.pe] Node Unique Local ID [PolicyCenter], Version [Server Agent v3.7.1.1 GA #2013-05-30_14-30-03 rfae6a263dfb6946da5ad0cfe1ddcb77ef384e43b 5]
[AD Thread Pool-Global1] 12 Jun 2013 00:25:53,060 ERROR ConfigurationChannel - Fatal transport error: paid29.saas.appdynamics.com
 
Could you help me please?

 

0 Karma

Arun_Dasetty
Super Champion

Hi,

Thanks for writing in. we see that you are trying to connect using 443 port and we see the controller https://paid29.saas.appdynamics.com:443/controller/ is accessible from our side.

Can you please provide    "<controller-ssl-enabled>true</controller-ssl-enabled>" flag set to true as follows in controller-info.xml under <agent_install_dir>/conf path in addition to controller-host, controller-port, application,tier and node , account-name and access-ket details if any, we suggested as we could not see ssl-enabled status from the stack trace provided hence we suspect this could be issue:
Ex: /opt/AppDynamicsPro/AppServerAgent/conf/controller-info.xml

 <!-- This specifies if the AppDynamics agent should use SSL(HTTPS) to connect to the Controller. If you set this to true,
    the controller port property above should be set to the HTTPs port of the Controller.
    This can be overridden with the system property '-Dappdynamics.controller.ssl.enabled' -->

Restart the server (with agent configured) after the above changes also make sure that paid29.saas.appdynamics.com is accessible from system in which agent is installed, you can try as follows to confirm whether controller is accessible from the machine on which agent is installed:

shell> wget paid29.saas.appdynamics.com

shell> telnet paid29.saas.appdynamics.com 443

Check the URL https://paid29.saas.appdynamics.com:443/controller/  is accessible from agent machine


, If you still see the issue, can you attach zipped version agent logs under directory /opt/AppDynamicsPro/AppServerAgent/ to debug further.

refer docs:

http://docs.appdynamics.com/display/PRO13S/Install+the+App+Agent+for+Java

http://docs.appdynamics.com/display/PRO13S/App+Agent+for+Java+Configuration+Properties#AppAgentforJa...

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Akumar.

I have the Edition PRO SAAS, my controller-info.xml I don't make any changes to that file.

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

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

<controller-ssl-enabled>true</controller-ssl-enabled>

<application-name></application-name>

<tier-name></tier-name>

<node-name></node-name>

<agent-runtime-dir></agent-runtime-dir>

<enable-orchestration>false</enable-orchestration>

<account-name>PacificoSeguros</account-name>
<account-access-key>My_key_password</account-access-key> 

<force-agent-registration>false</force-agent-registration>

 

When I do ping to paid29.saas.appdynamics.com did not resolve

Regards.

 

 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Can you please do ping pacificoseguros.saas.appdynamics.com and see if firewall is blocking it .

Also your your vanity url is http://pacificoseguros.saas.appdynamics.com/controller this so you can change in your controller info accordingly.

please change account name to pacificoseguros 

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...