Resolved. sorry I foundHi
Concern import/export DB
I have my 50Mb db from 4.0b3.
I would like to import to 6.35.rc12
I have try to import in cli. the command is accepted but nothing is done. and get Import done but nothing was done...
no errors...
what's wrong
Armand
oid("1.3.6.1.4.1.14988.1.1.3.10.0") / 10
Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properlyHow about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
Sorry for a stupid question but how to access the dude folder on my routeros?Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properlyHow about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
Use ftp. But the XML file cannot be used because there is db file like in v.4Sorry for a stupid question but how to access the dude folder on my routeros?Try copying the contents of folder /dude/data on your routeros server /dude folder. It worked properlyHow about .xml file?I can not import it.Always get "action timed out".The file size is about 150MB.
You must copy the contents of folder /dude/dataYes,there is a db file already in /dude folder on routeros created by default.I copied contents of data folder to dude folder in routeros,started the server,the server did some processing.After it finished,i started the server, tried to connect but nothing,no luck.Its empty
I did that first time just as you described.This morning,in my horor,i tried to connect and voala,the dude works.You must copy the contents of folder /dude/dataYes,there is a db file already in /dude folder on routeros created by default.I copied contents of data folder to dude folder in routeros,started the server,the server did some processing.After it finished,i started the server, tried to connect but nothing,no luck.Its empty
Don't copy the exported file
Disable dude server, copy to your default dude folder in routeros and enable dude server
Any update on this? Anything I can do to assist? Still exists in v6.34.2/v6.35rc12Changes in v6.35rc4 - v6.35rc9
* Fix various server crashes.
* Fix various db import crashes.
* Fix server crash on Agent configuration change.
@wincdaniel @vaidehi
We do have some hosts for which some of our servers also show parse failed status. Dev will take a look at that when he gets a chance.
You might have to just delete the probe and put it back on...Is there any way to clear the graphics files?
Possibly, but not on my end.Isnt there any write protection/rights problem?
Ok, a month has passed and noone has problems with vacuum-db on x86? I have just made an excercise with enlargement of dude storage disk to 2GB with 1964.4 MiB of free space and still having the same error. Now it is on 6.34.3. Removing the dude, wiping the disk, new database copy, nothing helped.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/viewtopic.php ... 97#p522497 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.
This issue has been completely resolved in (at least) RC42, maybe earlier.I don't have time to play too much right now to see exactly where the issue is, but I have tried 6.35RC29 and also RC30 with the same issue. I just exported and imported an old Hyper-V guest, updated to 6.35rc30 successfully, imported the current Dude database, and all is working fine.
I'll look into this issue some more when I get a chance...
+1Can we also change SNMP speeds (and any other spot for this) so I can just enter 100M instead of 100000000...
All those zeroes are tedious!
+1It would be great to add the feature to add more links to a map, an example is if I have a port channel to a map and want to monitor the ports separately.
Bump...G'day Krisjanis,
How is the progress on the Agent issue? Right now, it seems to be stalled. Whilst I can now add Agents without The Dude Client crashing and reloading with the added Agent not showing (and therefore not having been saved), there still seems no way to scan a remote network using an Agent. This feature is absolutely essential to have The Dude a useful network tool for monitoring my client networks, not simply their Internet connections.
The Dude is looking rather promising - I just hope development is progressing behind the scenes...
Thanx - resolved in 6.34.4Hi all,
i was move my Dude from windows server to MikroTik CCR1016-12G, Dude version 6.34.3.
All is fine, but syslog is not acceptable from devices, look like is not working
Syslog file is created but it's empty.
and after reboot i every time lost the Notification "Syslog", i recreat it and check the message by button "Test" it working.
and MikroTik CCR1016-12G not respond on 514 port. while syslog enable in menu.
in torch i see packets on 514 port from devices to mikrotik
NAT and Firewall filter not block the 514 port
on windows version of Dude it work fine
model CCR1016-12G
version ROS 6.34.3
firmware 3.27
serial 468702110059
Oh.Hey guys....
Can you please make a change to the CHANGELOG?
Please add a date/timestamp, plus the version # for that date/timestamp) for each change? At a minimum a date/timestamp.
THis gives everyone a more clear idea of what was fixed when, etc.
Thanks leon
Yes, I *do* like The Dude and really am glad that dev is once again happening with it. It has a lot of potential if things like the Agent issue (that I reported and asked again about just above) is addressed and progress keeps being made. An awesome little tool it is, for sure (potentially).The HD on the x86 system I run my ROS DUDE server on crashed today, and i feard i would have to struggle with moving the backup(Luckily I have standard regular routine of backup! ) over to the new DUDE.
...
Meanwhile I downloaded new client, and when it was done I filled in my credentials, and............... Voila my beloved DUDE emerges again from the dead on the new platform!
...
I am amazed how nice and smooth that worked out!
So my point? :
THANK YOU VERY MUCH MIKROTIK for bringing THE (AWSOME) DUDE back to life again, and making transition so painless!!! Even between system types!
Keep up the good work!
Cheers
Agreed. Would love the ability to have multiple links between devices.+1It would be great to add the feature to add more links to a map, an example is if I have a port channel to a map and want to monitor the ports separately.
I came across the same issue the other day...