AppD Archive

Waiting for Connection and cannot ping the controller......

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I am setting up the AppDynamics in our Tomcat 8 server, I installed the agent by following the instruction, but the page shows me 'Waiting for Connection', and I cannot ping the service by 'ping finnplay.saas.appdynamics.com'

PING paid150.saas.appdynamics.com (198.169.195.55) 56(84) bytes of data.

Please help us to check.

Thanks.

Br,

Yang

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Here is the traceroute...

traceroute to finnplay.saas.appdynamics.com (198.169.195.55), 30 hops max, 60 byte packets
1 hosted.by.shockmedia.nl (31.7.4.2) 0.382 ms 0.384 ms 0.453 ms
2 pc11.hgl2crt01.previder.net (62.165.125.17) 0.420 ms 0.526 ms 0.623 ms
3 te3-6.ams2crt01.previder.net (62.165.125.105) 2.429 ms 2.471 ms 2.504 ms
4 previder-2.telecity2.jointtransit.nl (217.170.9.90) 2.909 ms 2.861 ms 2.865 ms
5 adm-b2-link.telia.net (62.115.145.74) 3.179 ms 4.769 ms 3.322 ms
6 adm-bb4-link.telia.net (213.155.137.186) 2.525 ms adm-bb3-link.telia.net (62.115.141.62) 4.319 ms adm-bb4-link.telia.net (62.115.141.16) 8.690 ms
7 ldn-bb3-link.telia.net (62.115.136.147) 11.879 ms ldn-bb2-link.telia.net (62.115.136.199) 7.620 ms ldn-bb3-link.telia.net (62.115.134.25) 10.896 ms
8 nyk-bb1-link.telia.net (80.91.249.249) 82.803 ms nyk-bb2-link.telia.net (213.155.135.71) 116.800 ms nyk-bb1-link.telia.net (62.115.135.96) 86.165 ms
9 chi-b21-link.telia.net (80.91.246.164) 100.991 ms chi-b21-link.telia.net (62.115.140.67) 104.905 ms chi-b21-link.telia.net (62.115.137.53) 101.977 ms
10 servercentral-ic-312764-chi-b21.c.telia.net (62.115.58.30) 103.990 ms 102.810 ms servercentral-ic-312766-chi-b21.c.telia.net (62.115.58.34) 102.392 ms
11 ae4.cr1.ord6.us.scnet.net (204.93.204.85) 104.509 ms 104.118 ms 104.511 ms
12 ae2.ar10.ord6.us.scnet.net (204.93.204.81) 99.946 ms ae1.ar10.ord6.us.scnet.net (204.93.204.77) 103.854 ms ae1.ar9.ord6.us.scnet.net (204.93.204.75) 102.016 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi @Anonymous

Please see the solution posted to a similar issue that you are experiencing.

Let us know how it goes.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...