Closed avs262 closed 8 years ago
I've seen some issues with zabbix windows agents on hosts with relatively high number of guests and monitoring items, but it usually gives an "Interrupted system call" error. Regarding your issue I may suggest to run discovery via _zabbixget command from your zabbix server and see what it gives.
You may want to try setting the 'Timeout=' variable in the Zabbix agent's conf on each windows Hyper-V machine to something higher like 20 or 30 seconds. I believe the default timeout for the Zabbix agent (at least for the 3.0 agent) is 3 seconds which may be the problem.
Hi,
Ever see the 'timeout while executing shell script' notice for the VM discover items (zabbix server timeout is set to 30 seconds)? If so, what have you tweaked to resolve it? The 'zabbix-vm-perf.ps1' runs pretty quickly locally (~5 seconds).