On some of my 133c boards when I have opened up a new terminal I am getting Console has crashed or maybe system is completely busy; please log in again. Has anybody else seen this problem or know what is causing it.
2.9.46 - rb133c/r52h - 20 users approx - all on wireless. routerboard in routing mode, with masquerading. Console has crashed or maybe system is completely busy; please log in again.
Board routing approx 3 mbit with 3-4 simple queues, conn-tracking enabled, no firewall.
No mangle rules.
What could it be ?
Same with mac-telnet from directly linked mt.
edit: Will try net-install, as said in another topic.
Hi, I have same experience. It's low free memory problem in context with CPU load.At 4Mb free memory crashing bandwith-test command, at 3Mb stop working ping , traceroute commands,RB not answer on ICMP packets. At 2Mb crashing console and only winbox is usable. I hope RB133 with 32Mb don't have this problem.
No other packages enabled. No other actions.
Just masquerading a public address, with nat-ed clients.
Rebooted the rb, and did not appear since then. Also, having a similar experience with a rb112, i just put a script to reboot the rb every day. This way i will not get stucked if it fails. (meaning reboot every 24 hours since restart, since ntp is disabled. )
(Tried on another rb to put all the betas and the rc of 3.0 . All rc1-3 give me 100% cpu usage. sorry if off-topic.)
I am having the same issue on a 133c running .50 also. I acually "uninstalled" the usused packages instead of just disabling them, and that seems to have helped a little as my free memory went up slightly. But it does seem to be related to a "low memory" condition which causes the CPU to go to 100% for some reason. With the already limited amount of ram on these boards, I would think that ROS would be designed to be able to operate fine until it actually ran out of memory.
It makes me think that the same issue might be causing the problems when trying to run v3 on these boards. If 2.9 runs these boards right at the memory limits, I would think v3 would have slightly higher consumption which might be why we all see the cpu at 100% when trying the RC's.