Hi,
I was wondering if other people have the same issue as us or if someone could have a solution. We have upgrade our zabbix server to 5.2.6 from 5.0.11, the upgrade went well, we are able to pull datas from most of our sources that we had before the upgrade. But we get problems with the vmware template and his discovery rules. First when we were at the version 5.2.6, in zabbix logs, we could only see this logs lines as error:
zabbix-server_1 | 2021-05-12T10:35:36.835368900Z 281:20210512:063536.835 In vmware_service_init_hv() hvid:'host-xxxxx'
zabbix-server_1 | 2021-05-12T10:35:36.835373300Z 281:20210512:063536.835 In vmware_service_get_hv_data() guesthvid:'host-xxxxx'
zabbix-server_1 | 2021-05-12T10:35:36.839743700Z 281:20210512:063536.839 End of vmware_service_get_hv_data():FAIL
zabbix-server_1 | 2021-05-12T10:35:36.839786500Z 281:20210512:063536.839 End of vmware_service_init_hv():FAIL
So we tried to upgrade at the version 5.4 and now we have this line who speaks a bit more:
zabbix-server_1 | 2021-05-12T10:35:36.835364300Z 281:20210512:063536.835 Unable initialize hv host-xxxxx: Couldn't resolve host name.
So we search every possible thing that could prevent host to resolve, and we found nothing, something weird is when we go back to version 5.0 (from a snapshot) everything works perfectly.
We search a bit trough zabbix source code, and we found that zabbix is pulling new informations from vmware that it wasn't at the version 5.0.
Other weird thing to note is that some of our host(hypervisor) get discover with its datastores, metrics, VMs, etc... but only a few(5/15) of them. Could it be something that is activated on them and not the others ? (We already made a check and everything seems the same, maybe we missed it).
Our situation right is that we rolled back to version 5.0, and are running another zabbix version 5.2 in parallel to try to get the template discover every one of our hypervisor, VMs ,etc ...
If there's other thing you need to help us, tell us
I was wondering if other people have the same issue as us or if someone could have a solution. We have upgrade our zabbix server to 5.2.6 from 5.0.11, the upgrade went well, we are able to pull datas from most of our sources that we had before the upgrade. But we get problems with the vmware template and his discovery rules. First when we were at the version 5.2.6, in zabbix logs, we could only see this logs lines as error:
zabbix-server_1 | 2021-05-12T10:35:36.835368900Z 281:20210512:063536.835 In vmware_service_init_hv() hvid:'host-xxxxx'
zabbix-server_1 | 2021-05-12T10:35:36.835373300Z 281:20210512:063536.835 In vmware_service_get_hv_data() guesthvid:'host-xxxxx'
zabbix-server_1 | 2021-05-12T10:35:36.839743700Z 281:20210512:063536.839 End of vmware_service_get_hv_data():FAIL
zabbix-server_1 | 2021-05-12T10:35:36.839786500Z 281:20210512:063536.839 End of vmware_service_init_hv():FAIL
So we tried to upgrade at the version 5.4 and now we have this line who speaks a bit more:
zabbix-server_1 | 2021-05-12T10:35:36.835364300Z 281:20210512:063536.835 Unable initialize hv host-xxxxx: Couldn't resolve host name.
So we search every possible thing that could prevent host to resolve, and we found nothing, something weird is when we go back to version 5.0 (from a snapshot) everything works perfectly.
We search a bit trough zabbix source code, and we found that zabbix is pulling new informations from vmware that it wasn't at the version 5.0.
Other weird thing to note is that some of our host(hypervisor) get discover with its datastores, metrics, VMs, etc... but only a few(5/15) of them. Could it be something that is activated on them and not the others ? (We already made a check and everything seems the same, maybe we missed it).
Our situation right is that we rolled back to version 5.0, and are running another zabbix version 5.2 in parallel to try to get the template discover every one of our hypervisor, VMs ,etc ...
If there's other thing you need to help us, tell us