I have latest 2.1.7 with all needed compile keys installed.
./configure --with-libxml2 --enable-server --enable-agent --with-mysql --with-libcurl
When i add any vmware host, all LLD items become unsopported as soon as zabbix tries to fire them.
First i thought my problem is in { $URL} macro, tried all possible variants i can think off without success.
Then i fired up tcpdump and discovered that zabbix never tries to communicate to vmware host - no traffic at all. On the other hand there is no problem for zaabix to do that in other circumstances - if i add web scenario pointing to vmware URL like https://x.x.x.x/sdk/, tcpdump starts to see requests on wire.
Log isnt much help also - all i can get even with debugging enabled is
item [Vcenter:vmware.vcenter.hv.discovery[{$URL}]] became not supported: ZBX_NOTSUPPORTED
Any ideas where to look?
UPDATE
Downgraded to 2.1.5 and everything worked!
So, devs, look what you have broken in 2.1.5->2.1.7
./configure --with-libxml2 --enable-server --enable-agent --with-mysql --with-libcurl
When i add any vmware host, all LLD items become unsopported as soon as zabbix tries to fire them.
First i thought my problem is in { $URL} macro, tried all possible variants i can think off without success.
Then i fired up tcpdump and discovered that zabbix never tries to communicate to vmware host - no traffic at all. On the other hand there is no problem for zaabix to do that in other circumstances - if i add web scenario pointing to vmware URL like https://x.x.x.x/sdk/, tcpdump starts to see requests on wire.
Log isnt much help also - all i can get even with debugging enabled is
item [Vcenter:vmware.vcenter.hv.discovery[{$URL}]] became not supported: ZBX_NOTSUPPORTED
Any ideas where to look?
UPDATE
Downgraded to 2.1.5 and everything worked!
So, devs, look what you have broken in 2.1.5->2.1.7
Comment