Sorry for my absence from this thread.
Release early, release often being the open source mantra, I pushed a release out as soon as it did something.
I have plans to have it do much more (hence the device category, etc) including performance monitoring, and full VM details, but checking the hardware status is what I needed at the moment, and sadly all that I have had time to get to.
If you want to see exactly what it's calling as the zenoss user you can run the check_esxi.py script with the verbose argument and it will provide more details.
If you (or anyone else) wants to add functionality, it would be welcome, I can grant commit privileges for this zenpacks git instance (which I am hosting externally)
This zenpack is great, exactly what I've been looking for. I'm having problems with consistency. Using this to monitor 10 ESXi 4 servers and randomly they will fail with this error.
Cmd: /home/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://10.1.1.85:5989 root password - Code: 1 - Msg: General error
If I run the manual test sometimes it will be OK and sometimes I get Command timed out, DONE in 30 Seconds. My CommandTimeout in zProperties is set to 90 seconds. Is there another timeout setting I'm missing?
Anyone else run into this?
I too am getting many command timeout failures. To the point that I have to disable this template due to excessive false failures.
I increased zCommandLoginTimeout and zCommandCommandTimeout to 30 but still no joy, on monitoring 7 servers I receive approx 1 timeout per 30 min. Which is much too noisy.
From the command line, the request appears to work 100% of the time but from the command test page it fails maybe 1 out 5 times. Normally, the response comes back within 6 seconds.
Does anyone have a solution for this? Perhaps a WBEM setting?
Time: 2010/08/17 07:36:42.000
Command timed out on device 192.168.170.54: '/opt/zenoss/ZenPacks/ZenPacks.dnalley.VMwareESXi-1.0-py2.4.egg/ZenPacks/dnalley/VMwareESXi/check_esx_wbmem.py https://192.168.170.54:5989 <user> <password>
Message was edited by: tgrimm Provide sample error message.
I managed to get the failures down to an acceptable level.
I ran the "check_esx_wbmem.py" command looped manually for 60 iterations and timed each command execution. All requests returned OK, but a couple of the commands took over 1 minute to respond so my 30sec zCommandCommandTimeout was clearly not adequate.
I increased the timeout to 150 seconds and have not experienced any further command timeouts.
NOTE: I did receive _one_ General error over night and I feel this is acceptable for now.
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.