[ZBX-14858] Cannot collect VMWare when maxQueryMetrics is -1. Created: 2018 Sep 17  Updated: 2024 Apr 10  Resolved: 2019 Apr 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 4.0.0beta2, 4.0.1rc1
Fix Version/s: 3.0.26rc1, 4.0.2rc1, 4.2.0alpha1, 4.2 (plan)

Type: Problem report Priority: Major
Reporter: GuiGuiGui Assignee: Michael Veksler
Resolution: Fixed Votes: 3
Labels: vmware
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBX-14853 config.vpxd.stats.maxQueryMetrics Closed
Duplicate
is duplicated by ZBX-15315 Error of query maxQueryMetrics: 'conf... Closed
is duplicated by ZBX-16334 Error of query maxQueryMetrics: 'conf... Closed
Team: Team A
Team: Team A
Sprint: Sprint 46, Nov 2018
Story Points: 0.125

 Description   

Steps to reproduce:

  1. Set config.vpxd.stats.maxQueryMetrics to -1 as https://kb.vmware.com/s/article/2107096 suggest in solution step 7.
  2. Discover of VSphere

Result:
zabbix_server.log shows:

error reason for "VSpherehost:vmware.cluster.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.hv.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.vm.discovery[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.eventlog[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.fullname[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
error reason for "VSpherehost:vmware.version[\{$URL}]" changed: Cannot convert maxQueryMetrics from -1.
Expected:
We should be able to collect VMWare when the limit on query size is disabled or unlimited.

It should also collect when the limit is not specified (config.vpxd.stats.maxQueryMetrics not set)

 Comments   
Comment by Eduard [ 2018 Sep 26 ]

I have same problem on zabbix 4.0.0.rc1, 4.0.0rc2, 4.0.1

Comment by TAD [ 2018 Oct 03 ]

I have same problem on zabbix 4.0.0-2 LTS

Comment by Michael Veksler [ 2018 Nov 16 ]

Available in:

  • 4.0.2rc1 r86971,r87002
  • 4.2.0alpha1 (trunk) r86972,r87005
Comment by Marco Hofmann [ 2018 Nov 23 ]

Is this also fixed in 3.4.15? (We are still on 3.4 cause we are waiting for ZBXNEXT-4792)

Comment by dimir [ 2018 Dec 06 ]

starko, it wasn't fixed for 3.4, the fix should be available starting from 4.0.2 .

Comment by dimir [ 2018 Dec 06 ]

Yusev, so the problem still exists in 4.0.2? Could you please give more details on how you checked it?

Comment by Michael Veksler [ 2019 Mar 04 ]

Available in:

  • 3.0.26rc1 r90492
Comment by Edgar Akhmetshin [ 2019 Apr 08 ]

Hello,

The issue is persist on fresh new 4.2.0 install CentOS 7.6 from Zabbix official repo:

{
 24172:20190408:124849.116 In vmware_service_get_maxquerymetrics()
 24172:20190408:124849.121 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
 24172:20190408:124849.121 maxQueryMetrics used default value 64
 24172:20190408:124849.121 End of vmware_service_get_maxquerymetrics():SUCCEED
 24170:20190408:125149.188 In vmware_service_get_maxquerymetrics()
 24170:20190408:125149.191 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..
 24170:20190408:125149.192 maxQueryMetrics used default value 64
 24170:20190408:125149.192 End of vmware_service_get_maxquerymetrics():SUCCEED
}

Regards,
Edgar

Comment by Alexander Vladishev [ 2019 Apr 08 ]

edgar.akhmetshin, the scope of this issue is already released in the latest releases. Please create a new bug report.

Comment by Michael Veksler [ 2019 Apr 08 ]

This vmware responded to a regular property request. Which is the vcenter version?

Comment by Edgar Akhmetshin [ 2019 Apr 08 ]

Hello Michael,

vCenter 6.5 and 6.7

Regards,
Edgar

Comment by Michael Veksler [ 2019 Apr 08 ]

What about values from https://kb.vmware.com/s/article/2107096 ?

Comment by Michael Veksler [ 2019 Apr 08 ]

I agree that error text is not explained what happen - just show the vmware error. In fact the all works as expected, but not optimal (we use default 64 instead of 256 metrics per request).
This error means that you should explecitly define maxQueryMetrics to avoid performance degradation.

Generated at Fri Apr 19 19:18:45 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.