[ZBX-3441] server can reset disabled items to "not supported" state Created: 2011 Jan 20  Updated: 2017 May 30  Resolved: 2011 Oct 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 1.8.9, 1.9.7 (beta)

Type: Incident report Priority: Blocker
Reporter: richlv Assignee: dimir
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

in some cases, zabbix server can reset item from disabled to not supported state - seems to happen if item is disabled, then turns unsupported before configuration cache is updated

 Comments   
Comment by Alexei Vladishev [ 2011 Oct 12 ]

As a long term solution we should probably split item status (active, disabled) and not supported flag in the table structure.

Comment by richlv [ 2011 Oct 13 ]

...while thinking about possibility to set active/passive easily on a host/item level with items coming from one general template

also, wasn't there recently some work to make pollers use cache for unsupported state ?

Comment by dimir [ 2011 Oct 14 ]

Reproduced in latest 1.8:

  • disable item
  • before Zabbix agent cache is updated - make item unsupported
  • server sets item unsupported
  • item is processed according to "refresh unsupported"
Comment by dimir [ 2011 Oct 17 ]

Do not change the status of disabled item.

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-3441 .

Comment by dimir [ 2011 Oct 19 ]

Fixed in pre-1.8.9 r22512, pre-1.9.7 r22517

Generated at Thu Apr 25 17:57:19 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.