[ZBX-12696] An event does not occur when the item becomes "not supported" by monitoring via proxy. Created: 2017 Sep 08  Updated: 2018 Oct 09  Resolved: 2017 Sep 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.2.19, 3.0.10, 3.2.7, 3.4.1
Fix Version/s: 2.2.20rc1, 3.0.11rc1, 3.2.8rc1, 3.4.2rc1, 4.0.0alpha1, 4.0 (plan)

Type: Incident report Priority: Blocker
Reporter: Kazuo Ito Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: events, notsupported
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Events.png     PNG File ItemHistory.png    
Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 16
Story Points: 2

 Description   

This problem occurs when data is accumulated while Zabbix server and Zabbix proxy are unable to communicate and the item becomes "not supported" at the end.

1) Monitoring via Zabbix proxy Register host 'test'.
2) Register the item "test" of Zabbix trapper type of data type integer.
3) Register a trigger to generate a problem event when the retrieved value becomes 1.

4) Execute the following from Zabbix proxy.

]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o 0
zabbix_sender [2151]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.001339"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.001339"
sent: 1; skipped: 0; total: 1
]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o 1
zabbix_sender [2153]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.000044"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000044"
sent: 1; skipped: 0; total: 1
]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o 0
zabbix_sender [2155]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.000043"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000043"
sent: 1; skipped: 0; total: 1

5) Communication disconnection between Zabbix server and Zabbix proxy.

6) Execute the following from Zabbix proxy.

]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o 0
zabbix_sender [2162]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.000053"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000053"
sent: 1; skipped: 0; total: 1
]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o 1
zabbix_sender [2164]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.000044"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000044"
sent: 1; skipped: 0; total: 1
]# /usr/bin/zabbix_sender -vv -z 127.0.0.1 -s test -k test -o "a"
zabbix_sender [2166]: DEBUG: answer [{"response":"success","info":"processed: 0; failed: 1; total: 1; seconds spent: 0.000084"}]
info from server: "processed: 0; failed: 1; total: 1; seconds spent: 0.000084"
sent: 1; skipped: 0; total: 1
]#

7) Communication recovery between Zabbix server and Zabbix proxy.


Data is registered in the history.

No event occurs.



 Comments   
Comment by Alexander Vladishev [ 2017 Sep 08 ]

Confirmed on latest 2.2 r72324

wiper trunk seems to be working properly. Either there is more more complicated setup, or it was accentally fixed in some version (probably 3.4).

JKKim FYI : I confirmed this problem has occur on Zabbix 3.2.7. I have not check 3.4 yet, but maybe Zabbix 3.4 has another Issue from ZBX-12691.

vso I also confirm on 2.2

Comment by Andris Zeila [ 2017 Sep 11 ]

Successfully tested

However this will not properly work with ZBX-12251 fix, we should add subissue there.

vso added sub issue there.

Comment by Vladislavs Sokurenko [ 2017 Sep 11 ]

Fixed in:

  • pre-2.2.20rc1 r72456
  • pre-3.0.11rc1 r72459
  • pre-3.2.8rc1 r72460
  • pre-3.4.2rc1 r72463
  • pre-4.0.0apha1 (trunk) r72466
Generated at Fri Mar 29 11:08:53 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.