We're using the ZenPacks.community.VMwareESXiMonitorPython 3.0.3 (Jane's update to the perl sdk version of the zenpack) to monitor various esxi hosts.
We're occasionally seeing the python collector event being raised whereby it disables the datasource as it thinks the datasource is blocking for too long – as described in a couple of old threads:
When we see the event raised it is usually when hosts are being shutdown / started up (although not every time).
We've been experimenting with upping the blockingtimeout value to a large value (100+ seconds) to prevent this or setting the blockgintimeout to 0 to prevent the blocking watchdog from being started in PythonCollector...
but were wondering if anyone else has noticed the datasources from this ZenPack being blocked or any advice on how to avoid it?Thanks for any advice!
2018-12-07 14:57:53,178 INFO zen.python: plugins disabled by watchdog: ['ZenPacks.community.VMwareESXiMonitorPython.datasources.VMwareDataSource.VMwareDataSourcePlugin']2018-12-07 14:57:53,178 INFO zen.python: starting watchdog with 100.0s timeout2018-12-07 14:57:53,216 INFO zen.zenpython: Connecting to localhost:87892018-12-07 14:57:53,237 INFO zen.zenpython: Connected to the zenhub/0 instance
Hi,We're certainly affected by this.
Although pleasingly have not seen it for a while but then we have currently set the blocking timeout to 0, i.e. do not use blocking timeout! as we can't be in a situation where as there may not be access to zenoss by someone capable of unblocking it for some time.ThanksDafydd