Today, I upgraded our Dude from 3.6 to 4.0b2.
We use to monitor about 400 devices with about 200 links.
Nearly every link is being monitored by SNMP for bandwidth utilisation.
Directly after I’ve done the upgrade, everything seemed fine. (Seemingly the conversion of the database from v3 to v4 was successful)
But half an hour later running the freshly installed Dude4, the bandwidth charts weren’t filled with data anymore.
Furthermore, a file called dude.db-journal is growing larger over time and always has a current timestamp.
But the file called dude.db has no current timestamp and doesn’t grow over time.
Even worse: all changes I did to the maps and other settings in “The Dude” were lost, when I restarted the Dude-service.
The same happens, when I reboot the computer (WinXP 32bit, 1GB RAM).
I never experienced this kind of behaviour with The Dude 3.4 or 3.6 before.
Also the “Database Commit Interval” is set to 10secs.
Is there anything I could have done wrong?
EDIT:
what I also noticed was, that with the setting “only when local client is running” one instance of dude.exe remains in the processes list at nearly maximum CPU-load, even when I closed The-Dude Main application..
EDIT2:
CPU-Load with Dude4.0b2 always is 100% on the server, while it is 30% approx. with Dude3.6