As some other people has said in the thread http://forum.mikrotik.com/viewtopic.php?f=8&t=19536
my dude 3.0 beta7 stops monitoring or graphing.
So I have created a script wich restarts the dude service:
Code: Select all
@echo off
net stop "The Dude Server"
net start "The Dude Server"What I thougth:
The default probe interval is at 00:01:00 and has a timeout of 00:00:30, so I think that in the first 30 seconds of each minute the Dude is getting information.
After this it may take some seconds to write and consolidate data. May it be 10 seconds?
So I thougth that it would be safer to stop the process in the second 45 of the minute.
What it seems to happen:
The CPU for the dude.exe process is almost idle from the second 1 to 20 of each minute. After this, it has a peak followed by some activity till the second 5 of the following minute.
So I seems that it would be safer to stop the process in the second 6 of the minute.
The scale of the graph below, is as follows: a line of the grid is 3 1/3 seconds, and 3 squares of the grid are 10 seconds. The arrow of the mouse points to the second 22 of the minute. I have told you what I thought, but it looks I'm wrong. I also have told you what it seems to happen. Is there anybody who can tell us what's the truth?
