After updating from 2012r2.5 to 2.9 and installing nrpe-linux client the vmware API checks are broken.
I have searched, and this problem seems to be recurring since who knows when.
So far i have seen a lot of suggestions. None has solved my problem!!!
IT IS 100% SURE NOT A CREDENTIAL PROBLEM!!!!!
I can loginto virtual center without any problem with the used credentials.
Example: (and this was fully functional before updating)
/usr/local/nagios/libexec/check_esx3.pl -H my-host-ip -f "/usr/local/nagiosxi/etc/components/vmware/my-hostname_auth.txt" -l "VMFS"
Result:
ESX3 CRITICAL - Server version unavailable at 'https://my-host-ip:443/sdk/vimService.wsdl' at /usr/share/perl5/VMware/VICommon.pm line 551, <AUTH_FILE> line 2.
From what i have read the most likely cause is perl.
Does anyone have the real solution to this problem???
I would settle for a step by step manual of how to uninstall and reinstall the related components.
Please help me out!!!!!!
Kind regards,
Detronict, Rik Lijkendijk
check_esx3 broken
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: check_esx3 broken
Which version of the vmware sdk do you have currently installed, and which version of vcenter or vsphere are you checking against?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: check_esx3 broken
Hello Reinhardt,
Thank you for your reaction.
My installed SDK version before updating Nagios was 5.0.
I (partially) solved the problem.
The steps i took where:
1. Uninstall vSphere-CLI
2. (re)Install prerequisites and SDK 5.5 using the doc. "Nagios XI - Monitoring VMware With Nagios XI" Revision 1.0 - August, 2014
3. Update Redhat through yum.
Apparently the SDK is very picky about all kinds of dependencies, because after these steps and a reboot of the server the checks work again when executed bij the scheduler
However, when executing from commandline i still get an error. ( Login to VirtualCentre server failed: Error connecting to server at 'https://my-virtual-center-server/sdk/webService': Connection refused
The situation is workable, but it bugs me that i cant figure out why the command will not work directly from commandline.
Thank you for your reaction.
My installed SDK version before updating Nagios was 5.0.
I (partially) solved the problem.
The steps i took where:
1. Uninstall vSphere-CLI
2. (re)Install prerequisites and SDK 5.5 using the doc. "Nagios XI - Monitoring VMware With Nagios XI" Revision 1.0 - August, 2014
3. Update Redhat through yum.
Apparently the SDK is very picky about all kinds of dependencies, because after these steps and a reboot of the server the checks work again when executed bij the scheduler
However, when executing from commandline i still get an error. ( Login to VirtualCentre server failed: Error connecting to server at 'https://my-virtual-center-server/sdk/webService': Connection refused
The situation is workable, but it bugs me that i cant figure out why the command will not work directly from commandline.
Re: check_esx3 broken
Open the "check_esx3.pl" plugin in a text editor and add the following line to the top of the script (below the comments):
Save, exit and try your check again. Let me know if this helped. Thanks!
Code: Select all
$ENV{'PERL_LWP_SSL_VERIFY_HOSTNAME'} = 0;Be sure to check out our Knowledgebase for helpful articles and solutions!
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: check_esx3 broken
An alternative to look at is the box293_check_vmware plugin. It uses a vMA appliance to execute checks on which already has the SDK pre-installed.
box293_check_vmware can be downloaded here (along with a very detailed manual):
http://exchange.nagios.org/directory/Pl ... re/details
box293_check_vmware can be downloaded here (along with a very detailed manual):
http://exchange.nagios.org/directory/Pl ... re/details
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.