search

BaldMansMojo / check_vmware_esx

chech_vmware_esx Fork of check_vmware_api.pl
GNU General Public License v2.0
124 stars 67 forks source link

Critical! No result from CIM server.CIM server is probably not running or not running correctly! Please restart! #130

Closed baaleal closed 5 years ago

baaleal commented 6 years ago

Hi

We have the the next problem, the plugin get next info and the vm administrator answer us the CIM service is runnin ok.

/usr/lib64/nagios/plugins/check_vmware_esx -D 10.10.10.1 -f "/etc/nagios/objects/credential.cred" -S runtime -H esxsrv.local Critical! No result from CIM server.CIM server is probably not running or not running correctly! Please restart!

imagen imagen

imagen

imagen

Thanks for your help!

BaldMansMojo commented 6 years ago

We had that problem here too. CIM server reported running but when testing we found out that not all things were reported correctly. Restarting the CIM server fixed that problem. Therefore I put this message to the plugin.

Regards - Martin

bb-Ricardo commented 6 years ago

Hi,

We ran into the same problem with ESXi 6.5 hosts. Here was the issue that the health data in the CIM server output was set to undefined for some values.

That's why I added this commit: f530dd6963a0285e0d50dee7c1214b172d40ef77

BUT this also means you have to monitor your hardware separately through ILO/ILOM.

We especially had this issue with a HP DL580 G9. And botch ESXi images (vanilla vMware and HP custom image) had the same problem.

BaldMansMojo commented 5 years ago

Yep. We had it with Fujitsu Servers too. It was caused by the hardware agents Fujitsu deliverd for hardware information. We deinstalled the stuff and monitor the hardware now by management board.

Regards Martin

ant0nwax commented 5 years ago

Good day

we have 10 ESXi 6.5 hosts at the moment and on 9 of them monitoring works with vmware_check_esx, on 1 there is one select and subselect that does not work. ALL OF THESE 10 ESXI hosts DO NOT RUN CIM SERVER, still monitoring works on all of them, just not this one service:

root@monitoringsrv ~ # /usr/lib64/nagios/vmware/check_vmware_esx --host ch2-esxihost.subdomain.domain.tld --password [guesswhat] --select runtime --subselect health --sessionfiledir /var/spool/icinga2/tmp --sslport 443 --timeout 90 --username monitoring --trace=0 Critical! No result from CIM server.CIM server is probably not running or not running correctly! Please restart!

and if i start the sfcbd service, the hosts freezes :) need to unplug power from it :) even SOAP requests timeout then... [root@esxihost:] esxcli system wbem set --enable true [root@esxihost:] /etc/init.d/sfcbd-watchdog status sfcbd is running so this shall not run :) and it does not run on the other machines where it works

i know its not a bug in the monitoring script, just the error message is misleading since on the other hosts it does not show the error, monitoring is working, and CMI server is not running...

Happy for any thoughts and replies...

bb-Ricardo commented 5 years ago

Hi,

Yeah with 6.5 the health monitoring via VMWare is not the greatest to out it politely.

There should be a command option ‘—ignorehealth’ or so (please check the documentation to be sure) to avoid this issue. And yes I agree with you. A better error message would help a lot.

To monitor system health I could recommend my other project: https://github.com/bb-ricardo/check_redfish (currently tested with HP and Lenovo servers).