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
11-20-2020 02:58 PM - edited 11-20-2020 03:13 PM
We've been seeing this behavior since a recent reinstall of 4.5.10 where, after a day or two, the Machine Agent stops reporting metrics even thought availability looks ok. Investigation found errors in the logs complaining about having too many open files when trying to run extensions/scripts. Looking at open file descriptors for the process, it appears that it is leaking file handles for its own logs. I'm curious if anyone else has seen similar behavior recently.
From a test machine:
root@mm03:/proc/23667/fd# ps -ef | grep appd
root 11569 806 0 22:30 pts/0 00:00:00 grep --color=auto appd
root 23667 1 7 Nov18 ? 03:46:54 /opt/appdynamics/machine-agent//jre/bin/java -Dlog4j.configuration=file:/opt/appdynamics/machine-agent/conf/logging/log4j.xml -jar /opt/appdynamics/machine-agent/machineagent.jar
root@mm03:/proc/23667/fd# ls -l /proc/23667/fd | wc -l
4097
root@mm03:/proc/23667/fd# ls -l /proc/23667/fd | grep "machine-agent.log" | wc -l
3922
11-30-2020 07:43 AM
It looks like this behavior is related to a newly added Network Monitor extension in our deployment, though I don't have insight yet into why it is happening.
User | Count |
---|---|
3 | |
2 | |
2 | |
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