check_esxi_hardware.py fails after ESXI upgrade about check_esxi_hardware HOT 6 CLOSED

Hi Claudio Kuenzler,

Any findings please.

from check_esxi_hardware.

@palaniyappanpl I personally have not much time these days and need to finish paid work first. I will look at it as soon as I have time. Please also check the check_esxi_hardware monitoring plugin compatibility list.
Or, if it's really urgent, request a paid support on infiniroot.com.

from check_esxi_hardware.

Please run the plugin in verbose mode ( -v) and post the output here.

from check_esxi_hardware.

Hi, same issue on my side.
Here is the output after updating to pywbem 1.6.1:

20230804 15:34:15 LCD Status: True
20230804 15:34:15 Chassis Intrusion Status: True
20230804 15:34:15 Connection to https://x.x.x.x
20230804 15:34:15 Found pywbem version 1.6.1
20230804 15:34:15 Check classe OMC_SMASHFirmwareIdentity
Traceback (most recent call last):
File "/neteye/shared/monitoring/plugins/check_esxi_hardware.py", line 780, in
instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/local/lib/python3.6/site-packages/pywbem/_cim_operations.py", line 3066, in EnumerateInstances
PropertyList=PropertyList)
File "/usr/local/lib/python3.6/site-packages/pywbem/_cim_operations.py", line 1956, in _imethodcall
self, request_data, cimxml_headers)
File "/usr/local/lib/python3.6/site-packages/pywbem/_cim_http.py", line 501, in wbem_request
raise pywbem_requests_exception(exc, conn)
pywbem._exceptions.ConnectionError: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/neteye/shared/monitoring/plugins/check_esxi_hardware.py", line 781, in
except pywbem.cim_operations.CIMError as args:
AttributeError: module 'pywbem' has no attribute 'cim_operations'

from check_esxi_hardware.

@lucafwp Please open a new issue. The problem this issue is about was after a vSphere / ESXi upgrade. Yours seems to be after an upgrade of the pywbem module.

from check_esxi_hardware.

@palaniyappanpl The issue you reported is most likely caused by the ESXi upgrade itself. It removes additional local users, which you might have created for CIM monitoring. Please refer to the FAQ (https://www.claudiokuenzler.com/blog/308/check-esxi-hardware-faq-frequently-asked-questions).

from check_esxi_hardware.