Skip UNKNOWN status of a trigger ?

[simonc]

Hello all,

I've got 2 triggers, one check if a file exist and another one check a TCP port.

If the file exist, the trigger is ON and the second trigger is desactivate (with trigger dependency). I use it for maintenance.

If i reboot the monitored host, the triggers go in UNKNOWN state and then the TCP trigger goes ON. (because the dependence falls)

So, i'd like to skip the unknown state to keep my TCP trigger OFF (even if it's really ON...).

Any ideas ?

Thanks.

Kind regards.

[simonc]

i changed this on my "file exists" trigger today :

{host:vfs.file.exists[/home/user/maintenance].last(0)}=1 | ({TRIGGER.VALUE}=1&{host:vfs.file.exists[/home/user/maintenance].nodata(120)}=1)

It's seems to be better... I don't know if it's a really good solution. I will post here if it's not the case.

[simonc]

Try again...

This reduces the chances that the alarm is turned ON. But sometimes it turns ON anyway.

So my problem is not solved.

[MAKSA]

I noticed that this status appears after (in time) reboot the server part of zabbix. Most likely this is a bug