We have been running Dude for a couple years now and have never really run into any issues that we could not resolve or work around. So I would like to first off say thanks for this great product!
Dude 3.4 is running as a package under RouterOS 3.28 x86 currently. I have 2 backup stores setup as well.
This morning When I came in I tried to login and get “invalid password”. We have several accounts setup and all of them report invalid password. I rebooted the machine hoping it was just some memory glitch, but unfortunately the problem is still there.
I can rebuild our installation, but it will take several days/months to get it back to where it was. If anyone knows a way I can either reset the password from the RouterOS terminal or if you know what we are doing wrong, or if you have any other ideas to try… I would appreciate them. If not, then I will just begin to start over, I was just hoping someone could save me the time.
Also I think we had a power outage in the middle of the night last night, however the Dude server is ona battery backup and generator power source, and did not show that it ever lost power. There was a computer that was logged into the dude last night that did lose power however.
Thanks in advance for any assistance.
Update.
I was able to log in finally using the default user admin with no password. Once logged in I found that my maps were all gone. it was like a fresh install. Feeling I had nothing to lose I uninstalled the dude package and re-installed it. same results.
Then I remembered I had put two hard drives in this system and setup backup stores for the dude data. One of the drives had nothing on it, as it showed the same amounts of space free as the total available. The other showed 3 G of something on it. Wish I could look at it I thought. So I set it active, and rebooted the machine. I am now able to log into my dude with the old information and all my up to date information is there.
I was very relieved.
So, I decided to export my config quickly so I would have a backup. Everytime I try to export the config, after a few minutes of waiting for the export, I get kicked out of the dude altogether. about 3-5 minutes after that, I am able to log in and everything is fine. I have tried this about 20 times now. It simply will not let me export my data.
I also tried to copy it back to the primary master and set it active and it reacts in much the same way. kicks me, but when i try to copy/active it keeps me kicked out for about 10 minutes.
Any Ideas how I can get a backup of this data before I lose it forever? Aside from the obvious … creating a new server and copying it over manually.
It would be real nice if we could have access to the files in the stores. Is there a way to access them?
Update #2
If I keep working at this long enough I will solve all my own answers I guess without help from anyone else.
Thats ok, at least it will be posted here for someone else to benefit from hopefully.
The export seemed to be mad due to the fact the syslog file has become too large. we stream our syslog from our routers to the dude and they are getting very large for some reason (ill identify and correct that later but that is not related the this really, but the size might be the cause of the issues.)
So I deleted the old syslog files. there was about 25 of them each about 200megs or more.
I also deleted the old package update files that were no longer needed under the files section in the dude.
now the export works!
took about 4 minutes and then asked me where to save it.
so now i feel even more comfortable.
So I decided to copy the dude master to the dude secondary hdd (not the primary disk though) and it kicked me and took 5-10 minutes before it let me back in.
looks like there might be a bit of a bug there. unless there are undocumented limitations I was not aware of.