no system resources detail LOAD - you can see which process use CPU and Memory resources more.
every 3 hours CPU load on my router start raiseing to 100% and no way to catch why. try with torch - no strange traffic and no viruses, packets per second are around 1500-2000 like always.
this problem appears after upgrade from RO 2.9.8 to 2.9.9 - the strang thing is that only one from my two routers start makeing 100% LOAD
I think what he meant was something like the “top” command in Linux (which RouterOS is based on, after all). This is showing which process is using how much CPU time (and memory, …) right now.
Yes I agree, the top command would be useful but then I would also reveal what software was hidden in ROS! So I was mearly suggesting a technique that can be used today to get a history of load.
I suppose the fact that you’re (at least partly) exposing what’s running under the hood will be the fact that won’t make a “top” output happen in ROS.
But I think your suggestion with SNMP logging is missing the original posters’ point, as he is aware of a high load - he’s trying to find the reason for the high cpu load, and you could only achieve this by a display split by processes (to stay with the example) - not an overall load logging.
yes something like the “top” command in linux - the CPU load continues to grow to 100% every 2-3 hours and i can’t find what cause it. the only solution till now is reboot the router.
The license.txt file shows what components are in use … its not a secret really … just an excellent platform thats got a great team working it. I also agree, it would be nice sometimes to see what process was taking up CPU time, however if everything is running properly (like most of the time) you shouldn’t even care. In times of debugging though its a necessity pretty much.
CPU stays at 100%. Yep, I have been having the same problem. When you reboot the router, it starts out with anywhere around 10% but eventually it’s been reaching 100% and staying there. I honestly dont think it’s the real measurement. This has been only after upgrading to 2.9.8 from 2.8.27. May be a bug. Log has been going crazy too. We have syslog enabled for remote logging and even if you turn it off (system-logging), the log is not showing stuff.