Bureaucrats, confirmed, Administrators
4,558
edits
Changes
Jump to navigation
Jump to search
no edit summary
You'll probably receive alarms for 'tcp listen drops'. This is likely bot-related, and there is a good discussion on how to identify the source of the problem and how to mitigate or resolve it https://github.com/firehol/netdata/issues/3234
Following the advice from NASA at https://wiki.earthdata.nasa.gov/display/HDD/SOMAXCONN, I increased my somaxconn kernel parameter to 1024 from 128
<source lang="bash">
cat /proc/sys/net/core/somaxconn
128
sysctl -w net.core.somaxconn=1024
</source>
[[File:Tcp state diagram fixed.svg|600px|TCP State diagram]]
== Updates ==
Netdata will update itself, and puts a script into cron: <source lang="bash"code>
ln -s /root/netdata/netdata-updater.sh /etc/cron.daily/netdata-updater
</sourcecode>
[[Category:QualityBox]]
[[Category:Monitoring]]
