How much free space do I need on the disk in relation to dude db file size to make the dude database vacuum?
The dude status messages are very confusing.
In running state I run “vaccuum-db”. it tells: “status:running”.
Then print command tells: “disabling before vaccuum: stoped”.
Thinking I have to stop the dude first. So running “set enabled=no”
Getting status: “failure: vacuuming”
After a while the status is “running” again. checking the db file size - no change.
Stopping the dude “set enabled=no”.
Having status “status: applying settings: disabling: stopped”. What is it? Is the stopping stopped, or is the stopping in progress? Because dude process has left the profiler, I think the dude was stopped.
Running “vacuum-db” again. The steps are counting. To which number it should count to be sure everything went ok?
After a while the message: “status: vacuuming: failed database or disk is full”.
Now the point: dude.db file has 130,5MB. The disk used for dude storage has 247MB of free space. Why it is not enough? How much it should be?
Mikrotik, please, make the manual describing the dude usage in order to correspond to actual situation and covering all messages, commands and their relationship.
Sorry I am writing it again (originally here http://forum.mikrotik.com/t/v6-34-2-current-is-released/95555/10 as these notes apply to 6.34.2), but as this thread is referenced in the changelogs, I think it is better to mention it rather here…
And to write something positive/helpful to others too: Like others I had problems with importing the backup.tgz file from 4.b3 to 6.34.2. My solution that worked was to unpack the .tgz file and copy the content into dude store directory of ROS while dude was disabled. After enabling it looks like majority of the things work fine. Just the custom added functions reading oids are reported with problem “parse failed”. I do not know what to do with it so far.