Hi,

I am not 100% on this one and don't really want to take my live system down again to test but.......

RC14 installed on two RB333's. Ping watchdog tickbox set to off in winbox and double checked in terminal to show off. However the IP address to ping WAS filled in. I think this may be where the problem lies. So Normis et al, you might want to check what happens if the IP field is filled in but the tickbox is not set.

Regards,

Malcolm

Just tested RC13 - same bug here too.

I have a backhaul with IP watchdog. The link was disabled and I unchecked the tickbox to halt the watchdog. However the RB333's continue to reboot at both ends until the watchdog has the IP's removed totally.

Malcolm

I don't think you understand how the watchdog functions..

From the manual...

watch-address (IP address; default: none) - if set, the system will reboot in case 6 sequental pings to the given IP address (sent once per 10 seconds) will fail
none - disable this option

watchdog-timer (yes | no; default: no) - whether to reboot if system is unresponsive for a minute

The watchdog timer checkbox only disables checking of the Mikrotik system itself. It does not disable the monitoring of the watch-address.. To stop monitoring the watch address, you must remove the address.

-Gerard

Gerard,

Thanks for that - I did not realise that was the way it works.

Regards,

Malcolm

I have found that RC13 and RC14 do not create autosupport.rif in case of watchdog ...

[admin@MikroTik] > log print
00:01:55 watchdog,error,critical watchdog cannot ping address 10.10.10.1, rebooting
00:00:37 system,info,account user admin logged in via local

[admin@MikroTik] > system watchdog print
watch-address: 10.10.10.1
watchdog-timer: yes
no-ping-delay: 1m
automatic-supout: yes
auto-send-supout: no
[admin@MikroTik] >
[admin@MikroTik] > file print
# NAME TYPE SIZE CREATION-TIME

One more thing:
There is no way to remove smtp adress in watchdog:
[admin@MikroTik] > system watchdog set send-smtp-server=10.10.14.14
[admin@MikroTik] > system watchdog set send-smtp-server=""
invalid value for argument send-smtp-server
[admin@MikroTik] >

Only one way to do that is to setup 0.0.0.0 like smtp address
[admin@MikroTik] > system watchdog set send-smtp-server=0.0.0.0

Can anybody confirm this? Is this a bug?