Escalation-Notification even comes if trigger is still in normal state

[rrr]

I've activated escalation for an action. Notifying is working perfect if an action is active. But why did I receive still emails after the trigger is off?
Now I got ON/OFF-Mails and I don't know how to turn off this mailbombing....

And btw, how do I use this recovery message...?

[Alexei]

I assume you are running 1.6. Fresh install or upgrade? Please can you post a screen shot of your action.

[oneye]

I have same problems as rrr. I got bombarded with e-mail (trigger ON/OFF) although the host was down only ones. I don't know how to use recovery msg and escalations to other users/groups (like it is mentioned in the manual).

Thanks & regards

[oneye]

Here is the screenshot of what is happening.

[Alexei]

Thank you for the additional details. Please could you click on Filter in History of Events and select show unknown triggers.

Repost the screenshot here if the list of events differs from the previous one.

[oneye]

Here it is...

[tnk2k]

I can confirm this bug aswell.

-> i have on host / item / trigger / action (ping check)

zabbix escalates every minute which is good, but now i disable the host and thus the action should be disabled aswell(?, this is my conclusion as i can't find anything in the manual)), but it's not

[tnk2k]

Right,

Host -> Disabled
Item -> Disabled
Trigger -> Disabled
Action -> Disabled

Notifications are still coming in

[tnk2k]

The only way to stop it is by shutting down zabbix, now that sounds good.

[manowar]

Yes, can confirm I also see this. All worked great at first, then I ack'ed the alert and cleared the problem, then started the stream of OFF/ON alerts.

At the time there were the two entries in the escalation table. Stopping escalations and disabling the trigger seemed to let them clear.

[Alexei]

ZABBIX initiates a new escalation in case if a trigger event matches action conditions.

When a new event comes from the same trigger and it does not match the same list of conditions, escalation will be stopped.

In your case, you should add another condition "Trigger value = TRUE" to fix everything.

[alixen]

Thank you for the explanation

The probleme seems to has gone

But i asking myself, i didnt see another case of utilisation where we use this option to do something else ?

Thak you.

[manowar]

Thanks Alexei,

So setting the trigger condition "TRIGGER VALUE=PROBLEM" works well, and stope the continuing messages but now if I add "and "EVENT ACKNOWLEDGED = not ack" I still get messages even when the alert has been ack'ed.