Closed mhbates closed 7 months ago
I've been doing more research and it looks like there's a chance that this is a bug with the Transmission torrent client: https://github.com/transmission/transmission/issues/5385
It might just be coincidental that Netdata started reporting this for me recently; perhaps Netdata recently added this alert back in, or my setup with Transmission started to hit a point where it now triggers this bug. I'm going to try rolling Transmission back to 4.0.2 as mentioned in that linked issue and see if that helps.
@mhbates Did you find which process used 100% of its limit (according to Netdata)? You can do it by :
A screenshot from my server:
See 768
uses 20 FDs and it is 1.95%:
$ cat /proc/768/limits | grep "Max open files"
Max open files 1024 524288 files
=> 20 ÷ 1024 * 100 = 1.95%
This issue has been mentioned on the Netdata Community Forums. There might be relevant details there:
https://community.netdata.cloud/t/warning-alert-for-apps-group-file-descriptors-utilization/5278/3
This issue has been mentioned on the Netdata Community Forums. There might be relevant details there:
https://community.netdata.cloud/t/how-is-the-value-of-app-sql-fds-open-limit-calculated/5600/2
This issue has been mentioned on the Netdata Community Forums. There might be relevant details there:
https://community.netdata.cloud/t/app-sql-fds-open-limit-calculation-issue/5762/4
Bug description
Recently, starting around 3/28/24, I started getting a lot of these alerts for the "torrents" app group. What's strange is that I've since increased the open file limits in Ubuntu by many factors, and the particular limit for the individual docker container that I believe is triggering it on my end is even higher than the system-wide limits.
The open files limit for the docker container is 1,048,576. The soft limit system-wide is 8192, which is up from the default 1024. As I increase the soft and hard limits system-wide, I am not really seeing any change with Netdata's alerts; they're still getting triggered and still showing the same percentages as before.
Expected behavior
It feels like Netdata might be calculating these limits incorrectly and throwing alerts when it shouldn't be.
Steps to reproduce
Installation method
kickstart.sh
System info
Netdata build info
Additional info
No response