Several users of the Nagios plugin check_esxi_hardware.py have contacted me to tell me that the plugin seems broken after having installed ESXi 5.0 U1.
The plugin now takes several minutes to finish the check. In the verbose mode every CIM query (for each class) takes 5 seconds before returning the results.
After a couple of checks (thanks Pascal Saul) this 'slow bug' seems to come from the U1 update and is not related to the plugin.
This can easily be verified by using your own vSphere client. Open the Hardware Status tab of the affected ESXi server then click on 'Update' and you will see that it takes a very long time (~3min) until the hardware information is collected.
Update March 27th 2012 (1):
VMware has acknowledged the bug and forwarded the case to their engineers/developers.
Update March 27th 2012 (2):
The VMware devs already responded and they're working on a bugfix. But the fix will most likely not be finished/available until Q3 2012. Thanks again to Pascal for the updates.
Update March 29th 2012:
The bug can be tracked with the following ID: PR 855196
Update April 4th 2012:
The bugfix will be released in ESXi 5 Patch 3, which is unfortunately still only scheduled for Q3.
Update May 2nd 2012:
VMware released a new Knowledge Base (KB 2016538) entry where this bug is described.
Update July 17th 2012: VMware has fixed the bug. More information.
6uellerBpanda from wrote on Jul 25th, 2012:
bug fix confirmed. tried yesterday.
Phil from Worcester, UK wrote on Jul 13th, 2012:
VMware have released a patch for ESXi 5.0 which fixes this issue:
"VMware ESXi 5.0, Patch ESXi500-201207401-BG: Updates esx-base"
Claudio from CH wrote on Jun 5th, 2012:
Yes, you can increase the timeout in your Nagios service definition. I know from some users which do that as a temporary workaround.
Jose Antonio from Portugal wrote on Jun 5th, 2012:
Any workaround to solve this?
Any way to increase the timeout value?
Claudio from CH wrote on Mar 27th, 2012:
I'd like to but as I said, they only just acknowledged that it is a bug but don't know yet the reason. I'm quoting them:
'...something is different in ESXi 5.0 U1, but at this point we don't know what that may be or whether the issue can be easily addressed'
Eff Norwood from USA wrote on Mar 27th, 2012:
Can you please post the VMware bug number so we can track it? Thank you!
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Container Containers CouchDB DB DNS Database Docker ELK Elasticsearch Filebeat FreeBSD Galera GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb2 InfluxDB Internet Java KVM Kibana Kodi Kubernetes LTS LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Redis SSL Samba Seafile Security Shell SmartOS Solaris Surveillance SystemD Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder