No problem for one host - even if a trigger is active

[highway_fixer_man]

Hi,

I have about 100 that are in the same Host Group and have the same template assigned. The template has a working item called "Camera 1" calling on Key camara1.pingstatus which is a UserParameter as follows (I know camara is spelt wrong, its a hostname):

UserParameter=camara1.pingstatus,ping camara1 -c 1 -w 1 &>/dev/null; echo $?

If I get "100% packet loss" returned, I am using Preprocessing to change that to "Camera 1 Down" and if I get something else back, I am changing that to "Camera 1 OK"

This is working for 99% of my hosts in this host group. One host is not playing nice, and I would like to figure out why.

The camera on this particular host is confirmed down - and Zabbix has it as such in the latest data - but its not creating a problem.

Other hosts do have problems created if the camera is down. I just discovered this host was not creating a problem, even though it is a problem, as I was alerted to this camera being down manually.

If I check the problem history for this host - I actually do see that problems were created - but as the camera is still down, I would expect it to keep the problem open until its back online.

If anyone can give me tips or advise on what to try, I would appreciate it.

I have tried:

Restarting the agent on the host
Restarting zabbix-server

I have not yet removed and re-added the trigger, as I dont really know what that will do to historical data for other hosts.

Thanks in advance.

[LenR]

Make sure the host isn't in maintenance. You could unlink and clear that template from the host instead of removing the trigger from the template, that would only effect the history on this host. Beyond that, without seeing more, I don't know.