cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Machine Agent Leaking File Descriptors?

Elijah.Aydnwylde
Adventurer

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

1 REPLY 1

Elijah.Aydnwylde
Adventurer

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.

On-Demand Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here