how to save a log file in the dude log file menu?

RouterOS The Dude
1

Hello all,
We use a Dude software to monitoring mikrotik cpe.
We use Dude to monitoring our mikrotik cpe. We had create a log file for every cpe and configure cpe to send back their log on the dude server. All are working, we see all the log file of cpe in the dude log file menu.
The problem is when we restart the dude server, all the files disappear from the log file menu.
Who can tell if it is able to put back them or to protect (save) correctly the log file?

Best Regards,

2

Open the syslog menu, way over on the right side at the top click settings.
You should see the default is the dude keeps 10 syslog files.

I found an old syslog file in the following path…
\server\drive-C\Program Files\Dude\data\files\Syslog-2008.08.25-11.24.log

I suppose the dude is creating a new syslog each time you restart the dude.

I don’t use syslog but another thing that the dude can do is pass syslog along to another server.
Click on settings on the top left, select syslog, either edit the existing action to log to syslog or add a new action…

Let us all know if you have multiple syslog files in the dude folder and if a new one is generated when you start the dude.

Thanks
SD

3

Thank you sweetdude, our dude syslog don’t change when we restart.
What takes place it is that for an equipment “cpe01” for example, we have create the log file “log_cpe01”. Quite the configurations were made on the cpe on and on the dude so that log (event, info, system, etc.) is to record in this file “log_cpe01”. For that purpose, there is no problem, that works.
Now, when we restart the dude service or the server, we do not find any more the log file “log_cpe01” in the log files menu take off. It’s as if the config which were made was not to save .

4

I have seen odd things happen when you click “apply” instead of clicking “ok”.
Create your syslog and click OK and do not click apply.

Restart and see if it stays…

5

Oooh yeah, that is ok now.
Why makes that according to you?

6

The internal code that apply uses has a bug… Maybe we need a bug thread :slight_smile:

7

Okay. do you already have to use the 3.3 version?
I will make the upgrade to see if it corrects the problem.
Thank you sweetdude.

8

I don’t have any Router Boards. I am running dude 3.3 on w2k3 sp2. The dude 3.3 might have collection issues with Router boards. There is a thread about that. I did create a syslog2 on my server and it remained through a restart of the service. I don’t have any external servers so the problem could be just external servers. I just don’t have enough stuff to simulate your environment…

Have you restarted the server and still lose your settings after you hit just OK?