hi all,
while working with userparameters (referenz http://www.zabbix.com/forum/showthread.php?t=3144) i encountert a serious bug. i added a new case in UserParameter Script, cmta.sendmailmqueue[all] and added it to template. Of course i distributed the changed script to all hosts linked with the template but at this task i forgot one single host.
This host became Status 2 but no alarm or trigger was generated or got active.
unreachable {Template.name:status.min(120)}=2 is defined of course. Pls recheck but i guess zabbix is handling something wrong if script returns empty string. in this case the item should be gone unsupported but the host should be still active and other checks have to work. iam not sure if its just in the case of usig variables in UserParameter scripts or if its a templating issue because in the past without both conditions, items became unsupported like it supposed to be. i would debug myself but at the moment iam at heavy working load.
regards,
marc
while working with userparameters (referenz http://www.zabbix.com/forum/showthread.php?t=3144) i encountert a serious bug. i added a new case in UserParameter Script, cmta.sendmailmqueue[all] and added it to template. Of course i distributed the changed script to all hosts linked with the template but at this task i forgot one single host.
This host became Status 2 but no alarm or trigger was generated or got active.
unreachable {Template.name:status.min(120)}=2 is defined of course. Pls recheck but i guess zabbix is handling something wrong if script returns empty string. in this case the item should be gone unsupported but the host should be still active and other checks have to work. iam not sure if its just in the case of usig variables in UserParameter scripts or if its a templating issue because in the past without both conditions, items became unsupported like it supposed to be. i would debug myself but at the moment iam at heavy working load.
regards,
marc
Comment