Splunk AppDynamics

Cannot talk to the controller

CommunityUser
Splunk Employee
Splunk Employee

This is the error that I get below. I have turned off SSL and I am connecting to the SaaS controller on port 80. I can connect fine via my internet browser.

The application is a Java App and using a Jboss.

Where am I going wrong and what do I need to change to resolve this error?

[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,059 INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:8260, Name:appdynamics.ip.addresses, Value:10.204.30.117,fe80:0:0:0:8c84:6040:3171:9bb7%eth3,fe80:0:0:0:0:5efe:acc:1e75%net4, Name:supportsDevMode, Value:true]
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,059 INFO ConfigurationChannel - Sending Registration request with: Application Name [ACMEOnline], Tier Name [Inventory], Node Name [JBoss@LG007847:7800], Host Name [LG007847] Node Unique Local ID [JBoss@LG007847:7800], Version [Server Agent #4.5.5.24422 v4.5.5 GA compatible with 4.4.1.0 r6c48e890b0e5e4bdb691d9c7ded0d6cad742a64e master]
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,072 ERROR ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]: java.net.UnknownHostException: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,072 WARN ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [biker201812211313555.saas.appdynamics.com], port[80], exception [Fatal transport error while connecting to URL [/controller/instance/0/applicationConfiguration]]
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,072 WARN AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.singularity.CONFIG.ConfigurationChannel - java.net.UnknownHostException,2147483647]
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,072 WARN AgentErrorProcessor - 2 instance(s) remaining before error log is silenced
[AD Thread Pool-Global0] 30 Dec 2018 10:45:22,072 ERROR ConfigurationChannel - Exception: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
java.net.UnknownHostException: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server

Labels (1)
0 Karma

Naoto_Yamamoto
Path Finder

Hi Richard,

Thanks for posting the question on the Community.

Could you check your agent server’s firewall outbound setting? You need to allow outbound connections for these IP range:103.28.248.0/22 for your SaaS controller. This is documented in here: https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges


If it does not work, could you share your complete log directory?

Many thanks,

Naoto

0 Karma
Get Updates on the Splunk Community!

Uncovering Multi-Account Fraud with Splunk Banking Analytics

Last month, I met with a Senior Fraud Analyst at a nationally recognized bank to discuss their recent success ...

Secure Your Future: A Deep Dive into the Compliance and Security Enhancements for the ...

What has been announced?  In the blog, “Preparing your Splunk Environment for OpensSSL3,”we announced the ...

New This Month in Splunk Observability Cloud - Synthetic Monitoring updates, UI ...

This month, we’re delivering several platform, infrastructure, application and digital experience monitoring ...