VMware issue with update from 2.4.4 to 2.4.5

[dorsepp]

Hello together,

I searched everywhere but until now, nowbody have this problem with this version.

After I updated my Zabbix from 2.4.4 to 2.4.5 I have the problem that the status for my VMHosts is unknown. The strange thing here is, that not every host have this status.

I found this issues with other versions with the support remark that the problem is fixed since 2.3.

The question is now, does anybody have the same problem and maybe a solution or suggestion how I can fix this?

P.S. Log debugging is whitout any hint.
_________________
Zabbix 2.4.4
Ubuntu 14.04.2 LTS
MySQL 5.5.41
PHP 5.5.9

[Jason]

How many vmware discoverer processes do you have? I think need to have at least 2 after some changes were made...

[dorsepp]

Hi Jason,

thank you for your response. The discovery is successful, I can see every Host, but the item values are different. What exactly do you mean with discoverer processes. I can not find something like this in the config file.

Greetings Sepp

[dorsepp]

StartVMwareCollectors

Number of pre-forked vmware collector instances.

This value depends on the number of VMware services you are going to monitor. For the most cases this should be:

servicenum < StartVMwareCollectors < (servicenum * 2)
where servicenum is the number of VMware services. E. g. if you have 1 VMware service to monitor set StartVMwareCollectors to 2, if you have 3 VMware services, set it to 5.
Note that in most cases this value should not be less than 2 and should not be 2 times greater than the number of VMware services that you monitor. Also keep in mind that this value also depends on your VMware environment size and VMwareFrequency and VMwarePerfFrequency configuration parameters (see below).

Can someone explain me what exactly "VMware service" means? Is it the number of hosts I want to monitor? I have 71 hosts in my monitoring which is not working properly anymore. Maybe someone have a hint for me what I have to change in the config.

Thank you in advance.

Greetings

[gleepwurp]

Hi,

It's the number of "vCenters" you're querying...

From what I understand, the Configuration and Metrics are now separated into 2 different streams, if you're getting information from a single vCenter, you'd need at least 2 VMware Collectors at a minimum (one for configuration, one for metrics), and not more than 2 times the number of vCenters that you're monitoring VMs from.

Hope this helps,

G.

[dorsepp]

Now I understand it. That was my standard configuration because we use just one vCenter Server. Unfortunately it does not help so much because my main problem is not solved. But thank you for you explanation.

[gleepwurp]

Hi Dorsepp,

did you try changing the level of logging in the Zabbix server to 4?

ie:

DebugLevel=4

Change that (/etc/zabbix/zabbix_server.conf) and restart your server, and you should see your Vmware transactions go through and any errors encountered, which should help you figure out what's happening.

G.

PS: Of course, if the vmware discovery is executed from a Zabbix Proxy, the file to change would be /etc/zabbix/zabbix_proxy.conf on that proxy. Same for the "StartVMwareCollectors=2" if you only have one vCenter.

[dorsepp]

Hi,

sure I know this and I did this, but I do not really have a error I have wrong values and that is what I do not understand. In the version before everything was fine.