Steps to reproduce:

1. Create vcenter host. Add vmware template
2. Wait for a while, it shows the timeout messages
3. Raise the zabbix.conf file VMware timeout values
4. Modify the vcenter config.vpxd settings as written in https://kb.vmware.com/s/article/2107096 ( Value setted to -1)
5. Zabbix restart etc. Same result
6. Modify the vcenter config.vpxd settings as written in https://kb.vmware.com/s/article/2107096 to higher value instead of -1 ( like 3000 )
7. Zabbix restart etc. Same result

Result:
See screenshot...

We use the zabbix 4.0.5, customer's vcenter version is 6.5 U1

 

 

Config file

 

1. 1. 1. Option: StartVMwareCollectors
2. Number of pre-forked vmware collector instances.
   #
3. Mandatory: no
4. Range: 0-250
5. Default:
   StartVMwareCollectors=8

1. 1. 1. Option: VMwareFrequency
2. How often Zabbix will connect to VMware service to obtain a new data.
   #
3. Mandatory: no
4. Range: 10-86400
5. Default:
   VMwareFrequency=60

1. 1. 1. Option: VMwarePerfFrequency
2. How often Zabbix will connect to VMware service to obtain performance data.
   #
3. Mandatory: no
4. Range: 10-86400
5. Default:
   VMwarePerfFrequency=60

1. 1. 1. Option: VMwareCacheSize
2. Size of VMware cache, in bytes.
3. Shared memory size for storing VMware data.
4. Only used if VMware collectors are started.
   #
5. Mandatory: no
6. Range: 256K-2G
7. Default:
   VMwareCacheSize=128M

1. 1. 1. Option: VMwareTimeout
2. Specifies how many seconds vmware collector waits for response from VMware service.
   #
3. Mandatory: no
4. Range: 1-300
5. Default:
6. VMwareTimeout=300