check_esxi_hardware.py plugin issue

[bsivavani]

Hi,

We are using check_esxi_hardware.py plugin to check the esxi hardware health, we are getting CRITICAL error even though Memory is OK on server.

[nagios@XXXX libexec]$ ./check_esxi_hardware.py -H XXXX -U testusr -P 'testusr' -V hp
CRITICAL : Memory - Server: HP ProLiant BL460c Gen8 s/n: CZJ41801YW System BIOS: I31 2018-01-22
[nagios@XXXX libexec]$

Kindly advice ?

[lmiltchev]

What is the version of the plugin that you are currently using?

Code: Select all

./check_esxi_hardware.py --version

Do you see any additional (debugging) info, when you increase verbosity?

Code: Select all

./check_esxi_hardware.py -H XXXX -U testusr -P 'testusr' -V hp -v

Note: This plugin is not developed or maintained by us (Nagios). I will try to help but cannot guarantee that we will be able to resolve the issue. In order to speed up troubleshooting, I would recommend that you contact the plugin's owner as well.

[bsivavani]

What is the version of the plugin that you are currently using?

Code: Select all

./check_esxi_hardware.py --version

Please find version
[nagios@XXXX libexec]$ ./check_esxi_hardware_latest.py --version
check_esxi_hardware_latest.py 20190701
[nagios@XXXX libexec]$


Do you see any additional (debugging) info, when you increase verbosity?

Code: Select all

./check_esxi_hardware.py -H XXXX -U testusr -P 'testusr' -V hp -v

Please find attached plugin verbose output

Note: This plugin is not developed or maintained by us (Nagios). I will try to help but cannot guarantee that we will be able to resolve the issue. In order to speed up troubleshooting, I would recommend that you contact the plugin's owner as well.

[lmiltchev]

I see the following in the output:

20190711 11:47:20 Element Name = Memory
20190711 11:47:20 Element HealthState = 30
20190711 11:47:20 Global exit set to CRITICAL

I am not sure WHY the plugin reports the value of 30, however this is what it's causing the CRITICAL state.

According to vmware:

HealthState = 30 (Non-recoverable error)

https://blogs.vmware.com/vsphere/2010/0 ... art-3.html

This is what is used by the plugin:

30 : ExitCritical, # Non-recoverable Error

https://github.com/Napsty/check_esxi_ha ... ardware.py

Perhaps the author of the plugin can shed some light on the issue.