AppD Archive

DbAgent wont connect

CommunityUser
Splunk Employee
Splunk Employee

I am getting the following error trying to start my dbagent 

03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - using controller host [paid139.saas.appdynamics.com]; controller port [443]
03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting unique host information Host Name [ip-172-25-100-195]
03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent version [Database Agent v4.1.7.1 GA Build Date 2015-11-24]
03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent properties [{dbagent-name=Default Database Agent}]
03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent install dir [/opt/appdynamics/dbagent]
03:19:23,178  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent type [DB_AGENT]
03:19:23,179  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent application [Database Monitoring]
03:19:23,179  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent tier name [Database Monitoring]
03:19:23,179  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - setting agent node name [Database Monitoring]
03:19:23,179  INFO [<Default Database Agent>-Scheduler-1] DBAgent:46 - Sending Registration request
03:19:23,624 ERROR [<Default Database Agent>-Scheduler-1] DBAgent:30 - Fatal transport error while connecting to URL [/controller/instance/UNKNOWN_MACHINE_ID/systemagentregistration]: org.apache.http.NoHttpResponseException: paid139.saas.appdynamics.com:443 failed to respond
03:19:23,624  WARN [<Default Database Agent>-Scheduler-1] DBAgent:62 - Could not connect to the controller/invalid response from controller, cannot get registration information

I have a couple of Java agaents already running without issue but this DB one wont connect.

I searched for this problem and the general solution was to configure a proxy but i don't have a proxy and I can telnet to the URL and port 443 without issue.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I'm facing exactly the same problem. Able to telnet but the agent is not sending data to the controller.

0 Karma

Arun_Dasetty
Super Champion

Hi Vikram and Rob,

Apologies for the delay in response, if this still an issue, Check below:

- Does the host paid139.saas.appdynamics.com is reachable from db agent instance? did you provided account name and access-key , the error looks to be related network level , so check telnet or curl command output

shell> telnet paid139.saas.appdynamics.com 443

above command will confirm connectivity 

- does the ssl-enable setting is set to try as you are using https port 443, if not set it and restart it

sharing the agent logs should help us review the logs.

Regards

Arun

0 Karma
Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...