Triggers in Unknown State

[cva]

I'm having an odd problem with Triggers being in the UNKNOWN state which should not. For example, one of my Triggers is the default "Host has been restarted" ({Host.Unix:system.uptime.last(0)}<600). This trigger works correctly on all but one host where it reports UNKNOWN.

The odd part is that if I look at the alarms screen (clicking the date on the trigger) it shows the most recent alarm is for FALSE (not UNKNOWN).

I have a couple other items like this as well. They aren't all on the same host. It seems somewhat random.

Any ideas on how I could go about debugging this?

[nick5000]

I am having the same issue. If I disable and re-enable the triggers, they sometimes come back to regular operation. However, some have not. I'm running Zabbix v1.1. Is there something I can do to clean up the DB or try and figure out what is causing this?

Thanks,

Nick