Hi,
I ssh into my MT Box and do somthing - after /quit the CPU Load is at 100%. Only a reboot helps!
I have this problem on a RB800, RB433 and x86 all ROSv5RC1
velvet
BTW, any ETA for RC2?
Hi,
I ssh into my MT Box and do somthing - after /quit the CPU Load is at 100%. Only a reboot helps!
I have this problem on a RB800, RB433 and x86 all ROSv5RC1
velvet
BTW, any ETA for RC2?
just tried my RB800 on the table, login user with password, did something (/ip addr p; /ip ro p;/sy reso pri) then /quit
logging back in and everything is as usual.
log in:
[admin@x86] > /tool profile
NAME CPU USAGE
winbox all 0.5%
logging all 0.5%
management all 0.5%
idle all 98.5%
pppoe all 0%
unclassified all 0%
log out and log in again:
[admin@x86] > /tool profile
NAME CPU USAGE
ppp all 0%
firewall all 1.5%
logging all 0%
management all 53%
profiling all 14%
bridging all 1.5%
unclassified all 30%
I tested again on rb433 and rb800 and this time I waited few minutes - CPU is on2 % look good! only an my alix board CPU Load is still 100%
after 3 hours rb stop working with cpu usage 100%
only reboot helps for next 3 hours
after 5 mins CPU Load OK on rb433, CPU is at 100% again.
[admin@rb433] > /tool profile
NAME USAGE
wireless 0%
console 0.5%
dns 0%
winbox 0%
management 56.5%
profiling 0%
queuing 0%
unclassified 43%
have to find what that unclassified process is. as i see it ssh processes are identified correctly and that is something else that is using up your CPU.
the system is idle all the time until I ssh to the Box!
you can not reproduce it? login via ssh few times and /quit and you should see the 100% CPU Load.
I also have this problem but i am using Winbox … CPU Usage for “Management” goes very high (total CPU usage of the box is 100%) for a long time… only reboot really helps ![]()
this is fixed for 5rc2, so just wait for it.
yes, rc2 works for me!
Similar problem on Ros 5.0rc5. Please fix it.
I ssh into my MT Box and do somthing - after /quit the CPU Load is at 100%. Only a reboot helps!
Confirmed, same problem on RB433AH with ROS 5.0rc5.
After ‘quit’ from SSH session CPU is 100% busy.
Profile tool from Winbox shows:
management - 60%
unclassified - 40%
Next SSH connection, even without login reduces CPU utilization to typical level.
Regards, Grzegorz.
wait for 5.0rc6 release.