[ZBX-8008] Duplicate events Created: 2014 Mar 31 Updated: 2017 May 30 Resolved: 2014 Apr 17 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 2.0.11 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Minor |
| Reporter: | Łukasz Jernaś | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | duplicates, events | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
We're receiving duplicate events for our Zabbix trapper items in 2.0.11 and below. There are no unknown events in between according to the UI =2 It doesn't occur everytime, so we can't easily reproduce it. |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2014 Mar 31 ] |
|
Apparently, |
| Comment by Aleksandrs Saveljevs [ 2014 Mar 31 ] |
|
We had a similar problem, too:
Trigger configuration is as follows: {host:icmpping[,3,500].min(5m)}=1 & {host:agent.ping.nodata(5m)}=1 |
| Comment by Alexander Vladishev [ 2014 Apr 13 ] |
|
Hi, Your hosts are monitored through a proxy? It can be related to |
| Comment by Marc [ 2014 Apr 14 ] |
|
I notice frequently that events are generated out of sequence for a longer time: Beside being irritating for users this behavior may lead to wrongly triggered action operations. The affected hosts are monitored by proxies. |
| Comment by Marc [ 2014 Apr 14 ] |
| Comment by Łukasz Jernaś [ 2014 Apr 14 ] |
|
Ours are monitored by proxy too. Will |
| Comment by Alexander Vladishev [ 2014 Apr 14 ] |
|
Yes, |
| Comment by Alexander Vladishev [ 2014 Apr 17 ] |
|
I close the issue as duplicate of |