MikroTik

Since the last upgrade to v6.47, my Dude client crashes on a number of devices when I mouse over them in the Map view (charts start to appear and then client disconnects and starts reconnecting)
The same thing happens with when I try to view those device's details / settings screen -- Other devices are clean and work normally.

It appears to be related to some of the device's recorded chart data, because if I go into the "services" view, so no data is enumerated, and remove all the services on the device, then rediscover the services, that device will be fixed and work fine (at least for a bit).

I tried taking a Dude backup and using the sqlite3 DB's "obj" INSERT statements on a clean, new Dude DB (as described in https://wiki.mikrotik.com/wiki/Manual:T ... _db_repair) to remove all of the historical chart data, but the problem returned shortly after, even with all the historical data removed and 'fresh' devices created in the DB.

I've also tried playing with the rollup values (Raw keep time / 10 min / 2hr / 1 day rollup times) but it doesn't seem to have had any effect.

I have used the Dude for about 4 or 5 years now, and used to have a lot of historical data and a somewhat developed configuration for my environment. But given the recent problems I'm considering finding other monitoring solutions. I already trashed the old backup, so historical data doesn't matter now, but I'd really like The Dude client to stop crashing, and to be able to continue using it normally, again.

I'm experiencing the same on at least one of monitored devices.

It seems like it is related to recorded SNMP data, but the keeps recurring even after service data is removed, after some more logging occurs

I'd really like The Dude client to stop crashing, and to be able to continue using it normally, again.

Wouldn't we all...
But there's seemingly zero interest from the only people who can fix it.

at least file a bug report to support@mikrotik.com ...

Reported as well. Hope they will look into it. Current status simply means I can't use it at all and I don't know whether I should start looking for something else or not. Even with small bugs and lack of development, TheDude was much friendlier monitoring system than any other which I tried.

edit: According to support reply [SUP-20571], they were able to reproduce it (not surprising ) and they will look into it.

viewtopic.php?f=21&t=163482&p=805334#p805334

Thanks for the thought... I just tried deleting all disabled / inactive services... still crashes on a variety of devices.

I believe I narrowed the problem down to certain Data Sources. I have a lot of SNMP data sources and I think the recorded data gets botched sometimes, is probably the cause.

I found a workaround, since I have autodiscover profiles covering 99% of the service, I can remove all of the services from the Services view and let them be autopopulated when discovery runs.
I added the remaining services back in by hand.

So far the clean slate seems to be working. I suspect it's a matter of time until the crashes start again. I'll try and see if I can narrow it down to a particular service, then. It definitely seems to be SNMP or more granular data, rather than the latency times.

So, the problem came back an hour or two later. But it wasn't consistently reproducible, and just random / sporadic. And then some devices disappeared from the map. And some images, too. And then it seems like I started to hit every other bug and edge case that I've ever read about.

Deleting every service and adding them back in seems to work for a little while.

It does seem to have something to do with data from SNMP.
RouterOS devices always seem to break first in the Dude, and then high latency devices, and then others. Windows less often Linux or RouterOS, but they will still do it, too.

We are having same issue, roll back to 6.46.3 and the issue goes away, anything above 46.3 has this issue. I have been fighting this for 2 weeks, we are just using the older dude that cant read routers...

DUDE was broken in 46.4 when they changed DUDE stuff, no longer functions properly

I have the same problem as the OP. It exist from 6.47 and up to 6.47.2. Dude Client returns variety of errors:
connection closed
operation failed: 10053
operation failed: 10054
After downgrade to 6.46.6 again works like it should. I also narrowed it to drawing charts/service-history from old SNMP datasource. I hope it will be fixed soon.

+1 Please fix. this is urgent and should be high priority

After much research and testing it almost exclusively seems to be related to cpu/memory/disk/virt SNMP data sources, and possibly RouterOS ones, too.

I rolled back the Dude server to LTS (6.45.9), and had to switch all the RouterOS-integrated devices to SNMP, and anything monitored by remote agents to local dude server, and things seem to be OK now.

Would really like to see this addressed and some attention given to The Dude in an upcoming release...

Can this be seen as obvious hint that Dude application itself is at fault? Other versions of Dude work fine on this same "host machine".

My monitoring is also affected by the same. Very, very annoying!
Really hope it will be fixed in next release.

Same here, hoping to be fixed soon!

I have many custom services/sensors for devices and with them is The Dude is almost unusable. :-(

There is no chance to use older Dude client because it always download a new (actual)
version according to Dude server (package on RouterOS).

I got an info on my bug report [SUP-20571] that they resolved the issue and the fix will be released in upcoming RouterOS update.

Hurray :)

Yep, same here. ;-) [SUP-30054]

Hello

We hope that we have managed to resolve this problem. Unfortunately, the upgrade is required not only on the server but also on all of the monitored devices.

All of the upcoming RouterOS public releases will contain this fix.

Best regards
Mārtiņš S.

I have asked, what is meant by upgrading all monitored devices (I have many monitored linux servers via SNMP which causes crashes too) and got this reply:

Hello

Yes, all of the RouterOS powered devices must be upgraded - Dude server and all of the monitored devices that are running RouterOS.

Best regards
Mārtiņš S.

Does not make much sense, why upgrade all RouterOS boxes, while the problem is obvoiusly on the Dude side, but okay.

I didn't ask about this detail, but I assume, they are just pointing out the fact, that any TheDude Agent (any RouterOS device) must be same version as TheDude Server.
That is known requirement for TheDude Agents, but fortunately, if you don't want to use Agents, you don't need to upgrade monitored devices.

I am pretty sure that this is just wrong expression when they said "all of the monitored devices that are running RouterOS", because TheDude client is crashing even if I look at non-routerOS device (therefore nothing to do with monitored device itself)

Obviously, once the update is released, I will test it and refer back what is the reality

Exactly.
I was just curious about the "all of the monitored devices" in the first reply.
Looking for new version with fix every hour...

The new version - 6.48beta48 (2020-Oct-14 10:26) - looks promising! :-)
One Dude crash after update (on one device's Outages tab), but after client restart (invisible update), no crashes yet (mouse over, device properties, etc.)...
No need to update anything else (as I presumed). ;-)

I've upgraded our main Dude, and can confirm that this Bug is FIXED.

But offtopic, there is still problem when uploading new graphical files (.PNG or .SVG), they appear after quite some time. The only way that I found to force it to appear is to disable/enable Dude, but this cause a lot of false positives which is not good :)

RouterOS / Dude 6.47.6.
(6.47.7 is on hold due to lack of local justification from the change log contents.)

I'm seeing a client freeze pretty hard when trying to view charts all of the sudden tonight. I don't immediately see any other interfaces having this issue, but charts for latency monitoring and packet loss are the thing I use The Dude for every day...

Not being able to open charts is pretty breaking for me right now!

I see above that there's probably a fix in the 6.48 beta. I can't wait!

Thanks!

Sadly, several days after upgrade/reboot the situation is the same or even worse.

Dude 7.2.3 problem still exists.
I have configured some snmp probes in some devices. In most cases, when I click on one of those devices, the dude crashes with error 10053.
Really annoying.

useful workaround: reboot dude server

useful workaround: reboot dude server

doesn't work for me

I figured out that there is issue with the DB that causes that crashes.
Workaround is to export DB and import it again. In this process it has some kind of self repair mechanism.

Workaround is to export DB and import it again. In this process it has some kind of self repair mechanism.

This also doesn't work for me

Some news? Is there a solution to eliminate this annoying error?

Thx...

i have some suggested practices to improve behavior:
keep a limited ammount of data charts:
raw value keep time = 1 day + 8 hours
10min value keep time = 16 day
2 hour value keep time = 16 day + 1 hour
1 day value keep time = 16 day + 2 hour

when visualizing keep the interval under 3 days to avoid client crashing

dont forget to remove resolved outages regularly

i have some suggested practices to improve behavior:
keep a limited ammount of data charts:
raw value keep time = 1 day + 8 hours
10min value keep time = 16 day
2 hour value keep time = 16 day + 1 hour
1 day value keep time = 16 day + 2 hour

when visualizing keep the interval under 3 days to avoid client crashing

dont forget to remove resolved outages regularly

it actually helps. Crashes a lot less frequent, but it still don't resolve the issue, and lost of values is very costly workaround.

Is there a way to remove outages from a device without removing and re-adding the device? I can see there are lots of them, and Dude client disconnects when populating the list.