2017/11/01 15:11:33 [WARN] agent: check "service:nas-health" has the 'script' field, which has been deprecated and replaced with the 'args' field.
Thanks. Which FM BTW - FreeBSD?
Now I did find a bug report that relates to the note above but I did not connect them as it looks like I should have - https://bugs.freenas.org/issues/26355
I also now see the warning you pasted as the first warning in the logs after the reboot.
Thanks for the helpful comments.
Thx. I finally found it - I had used "search" for "nas-health" initially and found nothing, forgetting that the search feature in the manual may be a bit "weak".It's actually in the FreeNAS manual :)
(As per 5.10. Alert Services) doesn't it make sense that "nas-health" service only run if I have added at least one Alert Service and not at all if I have none?
Jan 19 01:32:25 NAS daemon[3288]: 2018/01/19 01:32:25 [WARN] agent: Check 'freenas_health' is now warning Jan 19 01:34:26 NAS daemon[3288]: 2018/01/19 01:34:26 [WARN] agent: Check 'freenas_health' is now warning Jan 19 01:36:26 NAS daemon[3288]: 2018/01/19 01:36:26 [WARN] agent: Check 'freenas_health' is now warning
service consul stop rm -rf /var/db/system/consul service consul start
{ "disable_update_check": true, "service": { "name": "nas-health", "tags": ["primary"], "address": "", "port": 80, "enableTagOverride": false, "check": [ { "id": "freenas_health", "name": "FreeNAS health check", "args": [ "/usr/local/etc/consul-checks/freenas_health.sh" ], "interval": "120s" } ] } }
"disable_update_check": true,
Yes, I noticed that it hasn't yet been fixed. I have no suggestion other than to stop the consul service.
{ "disable_update_check": true, "service": { "name": "nas-health", "tags": ["primary"], "address": "", "port": 80, "enableTagOverride": false, "check": [ { "id": "freenas_health", "name": "FreeNAS health check", "args": [ "/usr/local/etc/consul-checks/freenas_health.sh" ], "interval": "1800s" } ] } }
service consul stop rm -rf /var/db/system/consul service consul start
Jan 19 05:27:07 NAS daemon[13459]: 2018/01/19 05:27:07 [WARN] agent: Check 'freenas_health' is now warning Jan 19 05:57:07 NAS daemon[13459]: 2018/01/19 05:57:07 [WARN] agent: Check 'freenas_health' is now warning Jan 19 06:27:08 NAS daemon[13459]: 2018/01/19 06:27:08 [WARN] agent: Check 'freenas_health' is now warning Jan 19 06:57:09 NAS daemon[13459]: 2018/01/19 06:57:09 [WARN] agent: Check 'freenas_health' is now warning Jan 19 07:27:10 NAS daemon[13459]: 2018/01/19 07:27:10 [WARN] agent: Check 'freenas_health' is now warning Jan 19 07:57:10 NAS daemon[13459]: 2018/01/19 07:57:10 [WARN] agent: Check 'freenas_health' is now warning Jan 19 08:27:11 NAS daemon[13459]: 2018/01/19 08:27:11 [WARN] agent: Check 'freenas_health' is now warning Jan 19 08:57:12 NAS daemon[13459]: 2018/01/19 08:57:12 [WARN] agent: Check 'freenas_health' is now warning Jan 19 09:27:12 NAS daemon[13459]: 2018/01/19 09:27:12 [WARN] agent: Check 'freenas_health' is now warning
I did to and the messages seemed to have stopped.Yes - I rolled one machine back to 11.0-U4.