-
Incident report
-
Resolution: Fixed
-
Major
-
1.8.8
We have 2 items:
- "server unreachable (icmp)" (item: icmpping)
- "server unreachable (agent)" (item: agent.ping) witch depends on "server unreachable (icmp)"
The host went down. Trigger "server unreachable (icmp)" lights up as supposed to. Administrator ACK this trigger after he received SMS with this trigger.
Unfortunately trigger "server unreachable (agent)" reached and stuck in escalations. Zabbix started to sending SMSes to administrator with "server unreachable (agent)" trigger. There is no way to ACK this trigger, in zabbix GUI there is only "server unreachable (icmp)" already with ACK.
There was no "Deadlock found" in zabbix log related to this issue.
It is not easy to replicate this issue. It happens from time to time.
Specification: http://www.zabbix.org/wiki/Docs/specs/ZBX-4344
- is duplicated by
-
ZBX-10323 Notification still sent for Trigger after Trigger who is he depends on goes in Problem state
- Closed
-
ZBX-4835 Actions and triggers dependency problem
- Closed
-
ZBX-8667 Trigger dependencies ignored when a maintenance window expires
- Closed
-
ZBX-5796 Escalation emails are not behaving as expect
- Closed