Trouble monitoring VMWare

[nscott]

cwscribner,

Lets see if its an issue with wizard by bypassing it altogether. Can you go to nagios/libexec and run this:

./check_esx3.pl -H <ESX host> -u <user> -p <password> -l CPU

Does that return good status or does it say the SDK isn't installed properly? If this fails then we'll go back and take a closer look at the Perl modules/SDK install, otherwise we'll go the other direction and have a closer look at the wizard/configurations.

[cwscribner]

Per lmiltchev's request:

Code: Select all

-rwxrwxr-x 1 nagios nagcmd 5187 Sep 27 14:18 getguests.pl
-rw-r----- 1 nagios nagios 5187 Sep 27 14:18 growguest.pl
-rw-r----- 1 nagios nagios 2033 Sep 27 14:18 NagiosXI-VMWare.sh

Command execution:
On VMWare server

Code: Select all

ESX3 CRITICAL - Error: Cannot complete login due to an incorrect user name or password.

On VMWare guest

Code: Select all

ESX3 CRITICAL - Server version unavailable at 'https://172.22.X.XXX:443/sdk/vimService.wsdl' at /usr/lib/perl5/5.8.8/VMware/VICommon.pm line 545.

Just to refresh memory on the thread. I'm looking to see if a lack of login permissions will cause the SDK error in the wizard.

[mguthrie]

I'm assuming it would cause a problem. Have you tried it with a username and pw with login permissions?

[cwscribner]

I haven't yet. I'm waiting to hear back from my contact on getting the proper permissions added. I'll update when that's cleared up.

[cwscribner]

This is still an outstanding problem...unfortunately.

I managed to get the vCenter server monitored, but I can't get any of the other servers monitored. The vCenter admin set up the domain account in vCenter with admin privileges. Any thoughts on where to go next?

P.S. I think there's a bug in either the check_esx3 plugin or the vmware wizard. When addinf a vmware device through the wizard, the resulting auth.txt file contains the input user in both the username and password fields. i.e. username=nagios password=nagios instead of username=nagios password=password

[scottwilkerson]

P.S. I think there's a bug in either the check_esx3 plugin or the vmware wizard. When addinf a vmware device through the wizard, the resulting auth.txt file contains the input user in both the username and password fields. i.e. username=nagios password=nagios instead of username=nagios password=password

Yes there was, found it in the wizard. Thanks for pointing it out.
Updated wizard can be downloaded here
http://exchange.nagios.org/directory/Ad ... rd/details