VMWare Error

[mshpolar]

Hi there,

Has anyone run across this before on Zabbix 4.0?

1053:20190206:165700.534 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..

If so would you please share if you ever resolved it?

[Atsushi]

Is not it a bug fixed in 4.0.2?
Please tell me the detailed version of Zabbix you are using.

[mshpolar]

Ah yes, its Zabbix 4.0.3

[StevenBrs]

Hi there,

Did you ever find a solution ?

I'm running Zabbix 4.0.12 on centOS7, monitoring vCenter 6.7, and I'm seeing this error in /var/log/zabbix_server.log:

100422:20190916:132954.966 Error of query maxQueryMetrics: 'config.vpxd.stats.maxQueryMetrics' is invalid or exceeds the maximum number of characters permitted..

I tried setting config.vpxd.stats.MaxQueryMetrics = -1 on the vCenter appliance, and editing the /usr/lib/vmware-perfcharts/tc-instance/webapps/statsreport/WEB-INF/web.xml file setting maxQuerySize=0
but the error still occurs.

So, I was wondering
1. how I can get rid of this error
2. What is the impact of this error ? What info am I missing ?


Thanks in advance
Steven

[GustavGustav]

I have the same issue here. Also monitoring vcenter 6.7

Problem occured first on Zabbix 4.0.14 LTS (the first version that I ever installed, not sure about prior versions), yesterday I upgraded Zabbix to the latest version 4.4.4, but the issue is still occuring. OS is Debian 10 Buster, Zabbix is installed from official .deb repository.

I am aware of these related bug reports:

https://support.zabbix.com/browse/ZBX-15315

https://support.zabbix.com/browse/ZBX-14858

https://support.zabbix.com/browse/ZBX-14853

And this vmware documentation:

https://kb.vmware.com/s/article/2107096

That mention that the vcenter config.vpxd.stats.maxQueryMetrics value should be set to some other value than 0 or -1 to fix this.

Did that, now that value is set to 256. Also restarted the corresponding VMware Performance Charts Service, but Zabbix is still showing this error every minute in the logs.

How can this be further narrowed down or debugged?