Infrastructure (Server, Network, Database)

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal transport error while connecting to URL

Fatal transport error while connecting to URL

Hi,
I'm trying to monitor MySQL database on centos 7 using Trial license.
after configured conf/controller-info.xml, after that started  db-agent.jar .But on agent  log file I received below error:

18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:63 - setting agent hostname [XXX]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:67 - setting agent version [Database Agent v4.5.4.0 GA Build Date 2018-10-22]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:71 - setting agent properties [{dbagent-name=Default Database Agent, dbagent-launch-id=35d74525-0da6-4b89-a56b-1b141ec084a8}]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:75 - setting agent install dir [/usr/local/appdynamics/appdynamics-mysql-agent]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:79 - setting agent type [DB_AGENT]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:93 - setting agent application [Database Monitoring]
18 Feb 2019 08:21:11,705 INFO [DBAgent-1] RegistrationChannel:98 - setting agent tier name [Database Monitoring]
18 Feb 2019 08:21:11,706 INFO [DBAgent-1] RegistrationChannel:103 - setting agent node name [Database Monitoring]
18 Feb 2019 08:21:11,706 INFO [DBAgent-1] RegistrationChannel:46 - Sending Registration request
18 Feb 2019 08:21:11,706 WARN [DBAgent-1] RegistrationChannel:114 - Could not connect to the controller/invalid response from controller, cannot get registration information
18 Feb 2019 08:21:31,706 INFO [DBAgent-1] RegistrationChannel:57 - Controller host [castro2019021706554810.saas.appdynamics.com]; Controller port [443]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:63 - setting agent hostname [XXX]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:67 - setting agent version [Database Agent v4.5.4.0 GA Build Date 2018-10-22]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:71 - setting agent properties [{dbagent-name=Default Database Agent, dbagent-launch-id=35d74525-0da6-4b89-a56b-1b141ec084a8}]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:75 - setting agent install dir [/usr/local/appdynamics/appdynamics-mysql-agent]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:79 - setting agent type [DB_AGENT]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:93 - setting agent application [Database Monitoring]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:98 - setting agent tier name [Database Monitoring]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:103 - setting agent node name [Database Monitoring]
18 Feb 2019 08:21:31,707 INFO [DBAgent-1] RegistrationChannel:46 - Sending Registration request
18 Feb 2019 08:21:31,919 ERROR [DBAgent-1] ControllerHttpRequestResponse:30 - Fatal transport error while connecting to URL [/controller/instance/UNKNOWN_MACHINE_ID/systemagentregistration]: org.apache.http.NoHttpResponseException: castro2019021706554810.saas.appdynamics.com:443 failed to respond
18 Feb 2019 08:21:31,919 WARN [DBAgent-1] RegistrationChannel:114 - Could not connect to the controller/invalid response from controller, cannot get registration information

I disabled SSL and also I can telnet ZZZ.saas.appdynamics.com 433.

Best regards

Fatal transport error while connecting to URL
2 REPLIES 2

Re: Fatal transport error while connecting to URL

Hi Mahmoud,

I have been in a very similar situation, and the problem was in the order of the JVM parameters.

You could try with leaving the parameter "-jar db-agent.jar" at the very end of the java command line?

I.e.:

java -Dappdynamics.https.proxyPort=3128 -Dappdynamics.https.proxyHost=proxy.acme.com -Ddbagent.name="acmeDB" -jar db-agent.jar

At least it worked for me.

Best regards,

Mikel.

Highlighted

Re: Fatal transport error while connecting to URL

The above explanation should work