Actions firing on triggers that are not true

[ataylo13]

I had an issue over the weekend with the database, and now it seems that the actions are firing all the time. When looking at the dashboard, there are only 3 triggers active, yet I am receiving events for hundreds of hosts that are all working properly.

How can I track down what the issue is? This action has been in place for months without any major issues.

I tried restarting the zabbix_server process and that didn't fix the issue.

I have escalations enabled (every 5 mins)
Condition:
(A) Trigger severity >= "Average"
(B) Trigger value = "PROBLEM"

[simix]

I have a similar issue and in my case I get notification messages for triggers I didn't expect.

I have only one action with an operation 'send message'. The action condistions are
Type of calculation: AND
(A) Host = 'xxx.xxx.xxx'
(B) Trigger = 'Server xxx.xxx.xxx is unrechable'

I have expected to really get a message only if host xxx.xxx.xxx is unrechable, but that's not true. I also get messages for other triggers.

I either misunderstand how notifications work or somehow actions are not evaluated correctly.

Regards,
Simon

[Alexei]

(A) Host = 'xxx.xxx.xxx'
(B) Trigger = 'Server xxx.xxx.xxx is unrechable'

Add another condition:
(C) Trigger value = 'Problem'

Otherwise you will receive messages for all events: both problems and recovery.

[ataylo13]

Figured I would give an update:

I disabled the action for a bit while I was trying to figure out the issue. I found a patch for the memory leak in 1.6.2 and maybe these false positives are a side effect of the process consuming >5.1G of memory. I have restarted zabbix with the patched zabbix_server and re-enabled the action. Everything has been quite for a few hours now, so I will keep my fingers crossed.

[simix]

Add another condition:
(C) Trigger value = 'Problem'

Otherwise you will receive messages for all events: both problems and recovery.

Thanks Alexei. Maybe I wasn't clear enough. I understand that I get events for both problem and recovery. But I seem to get messages also for other host like this;

Processor load is too high on delta: PROBLEM

That has nothing to do with (A) Host = 'xxx.xxx.xxx' and (B) Trigger = 'Server xxx.xxx.xxx is unrechable' and still I get those messages. The trigger name is wrong and also the host is delta, not xxx.xxx.xxx.

Do you have any ideas why? I'm a very happy Zabbix user since the 1.0 days but now I simply can't find what's wrong. BTW, I using current 1.6pre snapshot but IIRC it was the same with plain 1.6.2.

[simix]

Ok, it doesn't happen again. Seems like I didn't wait long enough after changing action configuration.