ntopng after 2.9.0 update using all memory and cpu
-
After update to 2.9.0, I discovered, after a few hours, my memory jumped from 5% to 87% (of 32g), and top showing it was ntopng using it, and 67% cpu from 4%.
Disabling ntong, and rebooting, no issue with resources (it does requite a reboot to free the ram).
Easy to reproduce just by enabling ntopng and waiting a few hours.
Disabled:
Enabled:
-
@neccron99 Best initial guess is that ntopng just can’t keep up with all the stuff it’s being asked to do. Questions: Do you have a bunch of optional statistics enabled inside of ntopng? Are you monitoring unnecessary interfaces (LANs)? Do you have any form of active discovery enabled?
-
@dennypage 1) default 2) All lans [1-wan, 2 lan's], but only real activity is the wan and main lan. 3) no.
I have had ntopnd running for several years, and until this update, there has been no issues. -
@neccron99 said in ntopng after 2.9.0 update using all memory and cpu:
@dennypage 1) default 2) All lans [1-wan, 2 lan's], but only real activity is the wan and main lan. 3) no.
You should not monitor WAN. This results in double the amount of work. This is noted in the package config.
So just to be clear, "Network Discovery" and "Active Monitoring" show as disabled in the ntopng UI? Your Layer-7 Applications are None? Your Host Timeseries is "Light", and all other timeseries are disabled? All Telemetry is disabled?
How large are all the files in /var/db/ntopng?
Privacy Policy · Cookie Policy