Splunk AppDynamics

Unable to connect to the controller

CommunityUser
Splunk Employee
Splunk Employee

We connect to Appdynamics to SaaS controller on port 80, I was able to send application data to Appdynamics earlier and it was working fine. Now I see below error in logs,  please advise.

^ Post edited by @Ryan.Paredez for security reasons. Please do not share or attach log files to community posts.

Labels (3)

Alexander_Mash1
New Member

Anybody? I currently also face this trouble of "Connection back off limitation in effect".

0 Karma

Yogesh_Chouk
Builder

Hi Kiran,

Please let us know if there is any changes made on the controller side or the Agent side and then you started seeing this issue.

Could you please attach the provided the output of 

shell > curl -v https://<domain-name>.saas.appdynamics.com:80 or ping command output.

Thanks,

Yogesh

^Post edited by @Ryan.Paredez to remove mention of attaching logs to posts. Please do not share or attach logs to the community post

CommunityUser
Splunk Employee
Splunk Employee

Hi Yogesh,



It was working fine earlier, it stopped working recently. Attached is the log files folder.



ping deloitteapm.saas.appdynamics.com



Pinging myzgj.x.incapdns.net [message redacted to protect privacy] with 32 bytes of data:

[message redacted to protect privacy]


Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 213ms, Maximum = 215ms, Average = 214ms


I am able to telnet to [message redacted to protect privacy] on port 80.


0 Karma

Atyuha_Pal
Contributor

Hi,

[Information redacted for security reasons]

Thanks,

Atyuha

^ Post edited by @Ryan.Paredez to remove mention of attaching log files to community posts. Please do not attach or share log files to community posts.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

[Log file removed]

^ Post edited by @Ryan.Paredez for security reasons. Please do not share or attach log files to community posts.

CommunityUser
Splunk Employee
Splunk Employee

Anybody know why the below error is coming? Is it the problem with the account? I am able to telnet the controller on port 80. The integration was working fine, now it stopped working.

Below is the error I am getting:

[Information redacted]

^Post edited by @Ryan.Paredez to remove log files. Please do not share or attach log files to community posts for security and privacy reasons. 

CommunityUser
Splunk Employee
Splunk Employee

I am facing the same issue trying to port 80:

[Information redacted for security reasons]

^ Post edited by @Ryan.Paredez to remove log files. Please do not share or attach log files to community posts for security and privacy reasons.

0 Karma

Arun_Dasetty
Super Champion

Hi, Can you share (telnet <controllerhostname> <controllerport>) from agent host provide controller host and port used in the agent config? and also send the agent node logs folder archive for our review, email logs directly to my email id shared email in a different message.

CommunityUser
Splunk Employee
Splunk Employee

I am also facing the same: 

 org.apache.http.NoHttpResponseException: blah.saas.appdynamics.com:443 failed to respond
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Interestingly, trying to load the failed url in the browser (controller/instance/0/applicationConfiguration), chrome gets an error:

blah.saas.appdynamics.com didn’t send any data. ERR_EMPTY_RESPONSE

So I suspect the problem is on the controller end 😕
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

5 of us all expericing this problem. No response for 2 weeks. AppDynamics support, you listening?

0 Karma

Pratik_Maskey
Communicator

Hi Josh,

We need the exact SaaS URL you are hitting to check if there is an issue with the SaaS controller. Could you provide us the correct SaaS URL?

-Thanks

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Did any of you guys got the fix, as I too am facing the same issue. 

Regards,

Arun Koul

0 Karma

Stepheniel_Adia
Engager

Hi all,

Anyone had the chance to get this issue fixed?

0 Karma

Sai_Kumar_Kadiv
Engager

Hi 

delete logs try to copy controller info.xml  file in both conf and version check again after restart

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi, everybody!

Did you solve the issue?

I am facing the same error in one of ours servers:

2018-05-15 08:46:26.9604 5600 AppDynamics.Coordinator 1 11 Info CoordinatorService Stopped Machine Agent.
2018-05-15 08:46:28.3175 5600 AppDynamics.Coordinator 1 8 Info CoordinatorService Starting communicator...
2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator starting named pipe server
2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator named pipe = \\.\pipe\AppDynamicsAgentIPC
2018-05-15 08:51:26.0453 5600 AppDynamics.Coordinator 1 17 Info ControllerTimeSkewHandler Controller Time Skew Handler Run Aborted - Skew Check is Disabled

0 Karma

Ricardo_Huante
Engager

I'm currently having a similar issue

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...