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:
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?System rebooted because of ping watchdog timeout
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:
Code: Select all
/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
