BUG: Custom logs reseted to default after Windows reboot

RouterOS The Dude
1

Hi.
I created custom log instance and custom log notification.
After rebooting of Windows Server with Dude - logs are reset to default and I need to create them again and map Notification and log instance.
This bug persist in 3.4/3.5/3.6/4.0b2/4.0b3

The Dude 4 (beta)
Dude Server loses custom Syslogs
Dude Syslog BUG
Dude 4.0 beta4??
2

Please, post step by step procedure how to reproduce described problem.

3

Windows 2003 Server en + Dude 3.4
I installed Dude 3.6 over the 3.4 version.
In the result all my customs logs disapear, but notifications remained.

I can’t reboot this server. I will try to reproduce bug with reboot at home.

4

Windows XP Home En
Blank Dude 3.4

  1. Create New Log Instance - TestLog(with default settings)
  2. Create New Notification → TestLog -->Action=Log → Log=TestLog
  3. Create New Device - Device - IP(not existed) → Notification TestLog
  4. Wait until device will go down and alert placed in TestLog
  5. Reboot the Windows
  6. Start Dude and see logs - my TestLog desapiared, notification TestLog has left.
    Dude Running Mode - All time
    I have the same issue with service mode on my 4 Windows 2003 Server Eng.

File TestLog-2010.05.15-08.26.log exist in Data folder, but Dude will start new file when i create again TestLog log instance. This is not good.

5

Do you close the Dude client or just simply reboot the Windows?

6

Windows XP Home sp3 en:

  1. Running Mode = Only when local client is running

  2. Close Dude

  3. Restart Windows

  4. Log disapear

  5. Running Mode = All time

  6. Close Dude

  7. Restart Windows

  8. Log disapear

  9. Running Mode = As Service

  10. Close Dude

  11. Restart Windows

  12. Log disapear

  1. Running Mode = As Service
  2. Don’t Close Dude
  3. Restart Windows
  4. Log disapear
7

Thank you for the clarification. We will try to make tests and see where is the problem.

8

this bug persist in 4.0 beta1

9

Bag = http://www.google.com/images?q=bag&um=1&ie=UTF-8&source=og&sa=N&hl=en&tab=wi

Bug = http://www.google.com/images?um=1&hl=en&tbs=isch:1&sa=1&q=bug&aq=f&aqi=&aql=&oq=&gs_rfai=

10

And the bug is still in Beta 2…

11

No!

As you see, I have logs from november 8th, and I reboot the computer every day:

12

Excellent!
I have been created several instances in Logs, and all are still there after reboot! Naturally there is some short gap in logging during restart, but logging continues to fill in existing log file.

Now, we have a new question, imagine we have 50 log instances (logs) in Dude Syslog (50 routers) and we wanna create backup, as we usually do on weekly basis. This backup will be huge file since it will pull all log files. How we can create backup only with settings not with files? Is there some syntax with --exclude options for example?

We don`t need to include those files since we backup them using some scripts.

Thank you!

13

Actually we are quite satisfied with new .tar.gz backup format so there is no need to compress all those log files within dude separately since there are already compressed on proper way.

How we can automate backup, for example every day 5am run export and specify location? Is it possible using some command script and put it in scheduler (just like we pres export and specify location when dialog box prompts - two extraordinary simple steps)? I have been found some solutions related to previous versions of dude, must be some way to do this in 4.0x

14

just set it to “start new file: every day” and the old file will be saved in the defined location. this is configured in the “files” tab of the log settings in Dude.

15

thank you for reply normis, I know that, this is ok. But anyway we have to copy those old files each day and compress on backup storage, what can be accomplished now through new dude backup way - tar.gz.
Story is: by the new law we are obligated to keep certain log files up to 12 months (!), as we have many users and BS (MTIK) that would be few gigabytes log files each day. Initially I was thinking to create powershell script which will copy & compress only log files to backup storage, but now its easier to do everything with simple dude backup/export since everything will be already compressed, and compress ratio is excellent since log files are ordinary txt files, so more than 10GB will be few hundred MB.
Now I only need to automate two clicks - export and save to some location :slight_smile:. I cant accept someone will do that each day, no matter how it is simple - it would be stupid either :smiley:... However, if its not possible accomplish this through command line/script with dude (when Ill solve also dude itself backup procedure), Ill go back to powershell script.

Thank you.

16

Ah, so your request basically is to offer tar.gz compression for the log files?

17

Exactly, what we need → we already have with new backup procedure in 4.02 beta. No matter if everything is zipped (included rest of files), it would be all dude backup itself anyway, dozen MB every day more or less… Just to find out how to automate dude backup on daily basis…

18

Why do not you port this to windows?
http://forum.mikrotik.com/t/script-for-making-automatic-dude-backups-remotely/30447/1

19

Ok gsandul, now you move from karma No. 13 :slight_smile:…
it looks much easier now with http, so I have parameters for playing arround. I also opened inbound rule for web access in LAN. If I succeed with PowerShell script on my Win2008 I`ll post it here.

Thank you.

20

TNX, it was equal 13 for 1 day only :slight_smile: