[ZBX-14853] config.vpxd.stats.maxQueryMetrics Created: 2018 Sep 15 Updated: 2019 Mar 04 Resolved: 2018 Sep 28 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S), Templates (T) |
Affects Version/s: | 3.0.22 |
Fix Version/s: | 3.0.23rc1, 3.4.15rc1, 4.0.0rc3, 4.0 (plan) |
Type: | Problem report | Priority: | Critical |
Reporter: | Celio di Cavalcanti | Assignee: | Michael Veksler |
Resolution: | Fixed | Votes: | 15 |
Labels: | config.vpxd.stats.maxQueryMetrics, items, templates, vcenter, vmware | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Zabbix Server - Debian 8.11 ( |
Attachments: | VMWAre.PNG image-2018-09-17-07-49-12-485.png image.png test.PNG | ||||||||||||||||
Issue Links: |
|
||||||||||||||||
Team: | Team A | ||||||||||||||||
Sprint: | Sprint 43 | ||||||||||||||||
Story Points: | 1 |
Description |
After upgrade to version 3.0.22 many VMware items are not supported. 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted**
|
Comments |
Comment by gofree [ 2018 Sep 17 ] |
same for 3.4.14 - simillar situation was couple minor releases back - also with vmware items
tons of messages like this on the zabbix server
|
Comment by gofree [ 2018 Sep 17 ] |
|
Comment by Daniel Daniel [ 2018 Sep 17 ] |
3.4.14 on CentOS affected as well.
most probably caused by: https://support.zabbix.com/browse/ZBX-14775 |
Comment by gofree [ 2018 Sep 17 ] |
downgrading the proxy helped |
Comment by Daniel Daniel [ 2018 Sep 17 ] |
@gofree: I don't have there proxy in the affected env., just the 3.4.14 server, and I'm not that eager to screw it up somehow more by downgrading it whole do 3.4.13. |
Comment by gofree [ 2018 Sep 17 ] |
in my environment proxies are doing all the metric collection - server is just for notifications ans metrics evaluation - so the logical step was to downgrade just the proxy which is monitoring vmware environemnt - i know its not recommended but it worked in 3.4.11 vmware issue as well
i dont want to downgrade the whole stack either |
Comment by Marco Hofmann [ 2018 Sep 17 ] |
Can confirm: Debian 9 Stretch amd64 with Zabbix Proxy SQLite 3.4.14 affected. Downgraded to 3.4.13 and dropped the SQLite DB in between. Fixed the problem. |
Comment by Nick Oram [ 2018 Sep 17 ] |
Same Issue on Zabbix Appliance 4.0.0 Beta MySQL DB Edited. Solution in my next comment
|
Comment by Nick Oram [ 2018 Sep 17 ] |
To all with this issue, please see the following: https://kb.vmware.com/s/article/2107096 Please ensure the settings are set above in vCenter |
Comment by Celio di Cavalcanti [ 2018 Sep 18 ] |
Hi @lucanuk My vCenter parameter is set to -1 (unlimited). I believe that downgrade is the solution (workaroud). |
Comment by Celio di Cavalcanti [ 2018 Sep 18 ] |
Confirmed armv7l Proxy- after downgrade to 3.0.16 the problem solved. amd64 Proxy - after downgrade to 3.0.21 also works. Tks
|
Comment by Pascal Geneau [ 2018 Sep 18 ] |
Same issue here with Ubuntu 16.04 and Zabbix Server 3.4.14. Corrected by adding the config.vpxd.stats.maxQueryMetrics key on my Vmware Vcenter 6.0 Appliance. Thanks to @Nick Oram for the link above. |
Comment by gofree [ 2018 Sep 19 ] |
will this be handled in next release eg. can be ? |
Comment by Alexandre Mazovetski [ 2018 Sep 19 ] |
Same issue with Ubuntu 16.04 & ZS 3.4.14 & vCenter 6.5 (Windows). No solution by link of @Nick Oram |
Comment by Branin Lippincott [ 2018 Sep 19 ] |
Adding config.vpxd.stats.maxQueryMetrics to my vCenter and setting it to the default (256 on my 6.5 installation) fixed the Zabbix 3.4.14 problem. I assume downgrading Zabbix would have also "fixed" it. |
Comment by shingo shiki [ 2018 Sep 21 ] |
Hi All *Ubuntu 16.04.5 LTS MVekslers can you recall the previous values of maxQueryMetrics for vCenter and web.xml ? Hi Michael I confirmed it from a backup file. Before: After: MVekslers Thanks for your reply. Did you change the value in vCenter (not in web.xml) ?
I will answer your question. I have changed the two settings. 1.web.xml |
Comment by M. Possamai [ 2018 Sep 25 ] |
that's not a solution, that's a work-around. I've rolled back to 3.0.21. That worked. Hopefully this gets fixed soon in 3.0.23 |
Comment by Vladislavs Sokurenko [ 2018 Sep 28 ] |
Could be caused by |
Comment by Andris Zeila [ 2018 Sep 28 ] |
Please understand that the
error is what VMware returns when Zabbix tries to read config.vpxd.stats.maxQueryMetrics value to determine query limits. We are adding workaround to use default value 64 if this query fails, but better solution would be to configure VMware so correct limits could be obtained. |
Comment by Michael Veksler [ 2018 Sep 28 ] |
Available in:
|
Comment by Constantin Oshmyan [ 2018 Nov 23 ] |
Hi! The official documentation has currently the following note:
It is good. However, the mentioned article tells that the value "-1" for this parameter is a valid case:
The common sense suggests that "unlimited" is "more" than "64". 20523:20181122:161451.849 item "39373638-3935-5a43-4a38-30313436394e:vmware.hv.datastore.read[{$URL},{HOST.HOST},Tier1_Vesetas_VMFS5,latency]" became not supported: Cannot convert maxQueryMetrics from -1. 20525:20181122:161451.889 item "39373638-3935-5a43-4a37-3431304b4a31:vmware.hv.datastore.read[{$URL},{HOST.HOST},Tier1_Vesetas_VMFS5,latency]" became not supported: Cannot convert maxQueryMetrics from -1. 20526:20181122:161452.857 item "39373638-3935-5a43-4a38-30313436394e:vmware.hv.datastore.read[{$URL},{HOST.HOST},Tier1_DEAC_VMFS5,latency]" became not supported: Cannot convert maxQueryMetrics from -1. 20526:20181122:161452.857 item "39373638-3935-5a43-4a37-3431304b4a31:vmware.hv.datastore.read[{$URL},{HOST.HOST},Tier1_DEAC_VMFS5,latency]" became not supported: Cannot convert maxQueryMetrics from -1. 20525:20181122:161453.899 item "39373638-3935-5a43-4a38-30313436394e:vmware.hv.datastore.read[{$URL},{HOST.HOST},Tier1_Vesetas_vol2_VMFS5,latency]" became not supported: Cannot convert maxQueryMetrics from -1. My opinion is that Zabbix server should take into account the possibility of such setting, and have a more stable behaviour. |
Comment by Andris Zeila [ 2018 Nov 23 ] |
Yes, it was fixed in |
Comment by Constantin Oshmyan [ 2018 Nov 23 ] |
wiper, thank you for a good news! |
Comment by Michael Veksler [ 2019 Mar 04 ] |
The changes of |