[ZBX-6610] All checks are not collected on proxy because of corrupted IPMI check Created: 2013 May 16  Updated: 2023 Oct 11  Resolved: 2013 Jun 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 2.0.7rc1, 2.1.0
Fix Version/s: 2.0.7rc1, 2.1.0

Type: Incident report Priority: Critical
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File ipmi_error.log    
Issue Links:
Duplicate

 Description   

After ZBX-4991 if a host has corrupted IPMI check all Zabbix checks are not checked and Zabbix unreachable poller tries to get value from corrupted IPMI check every iteration. So Zabbix unreachable poller on proxy ignores CONFIG_UNREACHABLE_PERIOD and CONFIG_UNREACHABLE_DELAY. Look attached log file.



 Comments   
Comment by Alexey Pustovalov [ 2013 May 16 ]

Regression after ZBX-4991.

Comment by richlv [ 2013 Jun 04 ]

i assume this problem affects proxy only, server 2.0.6 is ok ?

<dotneft> you are right.

<richlv> and apparently problem only affects ipmi over proxy

Comment by dimir [ 2013 Jun 04 ]

Are you sure it's a regression introduced in ZBX-4991?

Comment by dimir [ 2013 Jun 05 ]

I confirm that this is a regression introduced in ZBX-4991. Invalid value for ipmi_disable_until is set in the cache.

Comment by dimir [ 2013 Jun 05 ]

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

Same problem exists in trunk.

Comment by Alexander Vladishev [ 2013 Jun 12 ]

Successfully tested!

Comment by dimir [ 2013 Jun 12 ]

Fixed in

  • pre-2.0.7 r36261 (introduced in 2.0.6)
  • pre-2.1.0 r36263 (introduced in the same version).
Generated at Thu Apr 25 11:00:25 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.