Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
03-04-2018 09:03 PM - last edited on 12-04-2019 01:26 PM by Ryan.Paredez
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.
03-06-2018 07:56 PM - last edited on 12-11-2019 10:31 AM by Ryan.Paredez
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
03-06-2018
10:04 PM
- last edited on
01-30-2019
04:46 PM
by
Radhika.Puthiye
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.
03-07-2018 11:14 AM - last edited on 12-11-2019 10:33 AM by Ryan.Paredez
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.
03-08-2018 04:19 AM - last edited on 12-04-2019 01:28 PM by Ryan.Paredez
[Log file removed]
^ Post edited by @Ryan.Paredez for security reasons. Please do not share or attach log files to community posts.
03-08-2018 10:21 PM - last edited on 12-09-2019 10:34 AM by Ryan.Paredez
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.
05-14-2018 06:16 PM
I'm currently having a similar issue
05-15-2018 04:56 AM
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
06-06-2018 06:22 AM
Anybody? I currently also face this trouble of "Connection back off limitation in effect".
07-03-2018 10:28 AM
I am also facing the same:
org.apache.http.NoHttpResponseException: blah.saas.appdynamics.com:443 failed to respond
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form