The Dude causes CPU to go to 100%

I have always had this issue but the more I get the dude monitoring the worse it gets.

When setting up a new device to monitor the first hour or so after setting it up if I double click on it I get the main screen for the device but all the menu on the right is missing and clear and The Dude Freezes. If I CTRL ALT DEL and look at CPU % its at 100% all used by THe Dude. After a min or two it goes back to normal and I can adjust a devices settings. As soon as I hit apply, it freezes again. Once i fight through this and have a new device setup I have no more issues with it after that. All i do is ping and snmp on my UBNT devices and same + routeros on MTik products.

which version of the dude do you use, what machine is it installed on, is the server and client program running on the same device?

Dude 3.6 Running Server as service. Client can be on same system or remote.

Dude server: Pentium 4 2Ghz 512MB. Have tried multiple netcards even Intel Pro1000.

Public IP, using local RB493AH for DNS.

Seems to hang on either DNS, SNMP, or Polling. Can figure out which.

Also from the dude I get <1ms Ping to most everything until there is a big jump.

Steve

Unresolved Please Help

Same issue here.
I get the same issue on multiple computers. Only using ping as a service. Anyone found a fix yet.

If you are running dude before 4.x there is a strange SNMP bug that would add a great number of nonexistent probes to a new device.

The quick way to fix that was to delete the device and then click undo. Is this the issue you are running into?

Be brave, use Dude 4 beta2. CPU goes to 100% when it is performing some sort of management tasks. These tasks seem to ensure database integrity, and overall system integrity. You can view the CPU profile and watch what is using the CPU. Bandwidth graphs and other things will restore properly after the CPU settles down to normal level, AND, rebooting Dude machine. (This is for Dude on x86 RouterOS)

Also, the old add device and client hangs hasnt happened in a long time, which seems to be what was being described.

Operating Dude4beta2 on RouterOS with success. Many features are now requirements for me.

Export/backup of Dude is tricky. Do it on the fastest network connection possible. Also, Dude will seem to act unstable during and after export. Just pay attention to client and server bandwidth stats and task description. It will look like connection is broken, but suddenly prompt you for the save. When dialog box for save appears, be quick to save file, real quick…Stuffing keyboard buffer with enter sometimes will accomplish the save. Finding the file might be fun, but seems to go to desktop, at least the first time. Makes it easier to find the elusive tgz backup file. Still a little dicey, but it works. Reboot RouterOS box (x86 in my case), and wait for CPU to settle, and all should be well. Again, you gotta be a little brave and quick on the trigger… :sunglasses: