Netwatch script no longer working in ROS 7.15

Hi folks,

I have a script that runs as part of a Netwatch test, that I use to failover between 2 MTK devices that are in VRRP configuration. This script has been working fine till 7.15 or so but now it fails with the error:

executing script from netwatch failed, please check it manually

Currently script permissions are set to “read,write,reboot,test” as per the docs. Script content is as follows:

# Raise priority of all VRRP Interfaces
# This failover script only works when two routers are each individually connected to a 
# single internet connection. A different approach is needed when a single router
# is managing failover across two interfaces
/interface vrrp set priority=250 [/interface vrrp find vrid=20]
/interface vrrp set priority=250 [/interface vrrp find vrid=48]
/interface vrrp set priority=250 [/interface vrrp find vrid=50]
/interface vrrp set priority=250 [/interface vrrp find vrid=54]
/interface vrrp set priority=250 [/interface vrrp find vrid=67]
/interface vrrp set priority=250 [/interface vrrp find vrid=75]
/interface vrrp set priority=250 [/interface vrrp find vrid=83]
/interface vrrp set priority=250 [/interface vrrp find vrid=104]
/interface vrrp set priority=250 [/interface vrrp find vrid=122]

/ip dhcp-server enable [/ip dhcp-server find address-pool=mgmt-iprange]

Can anyone tell me why this script has stopped working and how do I get it working again?

Likely it does work, but throws an error nonetheless, it seems like it is a new “feature” of 7.15, check starting from here:
http://forum.mikrotik.com/t/v7-15-3-stable-is-released/176334/1
and keep an eye on that thread, it is likely that a solution or a workaround will come out, no idea what the reason could be in your simple script, though.

Check that all the referenced vrrp interfaces and the DHCP server actually do exist…
Usually this is about long standing issues, that just have not been reported before.

I’ve eyeballed the list of VRRP ID’s & the dhcp-pool name and I’m not seeing anything wrong, but it could just be I’m missing the obvious here:

Indeed if I run the script from the terminal with the new “use-script-permissions” option, it appears to run without any problem:

/system/script/run vrrp-up use-script-permissions