Watchdog log entries

RouterOS General
1

I have Watchdog set up as shown below.

I notice that when a Watchdown timeout occurs, the MT device reboots but (1) I don’t get a supout emailed and (2) I get the following in the log upon booting up:

System rebooted because of ping watchdog timeout

How can I either get a log entry that persists a reboot, or an email telling me that at xx:xx:xx time the Watchdog timer has timed out and is going to reboot the system now?

Interestingly, when I open a New Terminal, I see these messages – so the information on rebooting due to watchdog timeout persists the reboot (somewhere):

(1 messages not shown)
2024-04-11 12:26:58 system,critical,info ntp change time Apr/11/2024 12:26:36 => Apr/11/2024 12:26:58
2024-04-11 23:59:42 system,error,critical System rebooted because of ping watchdog timeout
2024-04-12 00:03:47 system,critical,info ntp change time Apr/12/2024 00:03:25 => Apr/12/2024 00:03:47
2024-04-12 00:16:00 system,error,critical System rebooted because of ping watchdog timeout
2024-04-12 00:19:22 system,critical,info ntp change time Apr/12/2024 00:19:00 => Apr/12/2024 00:19:22
2024-04-12 01:13:06 system,error,critical System rebooted because of ping watchdog timeout
2024-04-12 01:19:23 system,critical,info ntp change time Apr/12/2024 01:19:01 => Apr/12/2024 01:19:23
2024-04-12 05:29:56 system,error,critical login failure for user admin from 192.168.2.22 via winbox

Watchdog config:

/system watchdog
set auto-send-supout=yes ping-start-after-boot=10m ping-timeout=5m send-email-from=joseph@xxxx.com send-email-to=\
    joseph@xxxx.com watch-address=1.1.1.1

Thank you.

2

No solutions?

3

Any way to create a log entry that persists a reboot when watchdog is about to reboot?

Or send an email with date/time?

4

I should have been clear in my other post. I think the email is only generated when a supout is generated and supout is only generated if there is a hang/etc. Docs say:

Watchdog reboot is not a system failure. Such reboot also will not generate autosupout file. Watchdog reboot is “/system reboot” automatically triggered by operating system when some service is not responding as fast as it should.

If you need an email, you can use netwatch with a script, using some interval less than watchdog pings. And since logs go to memory, only option is an external syslog server. But again if watchdog is trigger because ping fail, email or syslog may not work either.

5

Maybe schedule a script that run at startup and check log or other things and mail supout file if any with information after watchdog reboot.