Cheshire Cat Computing

I installed "Icinga 1.0.2". I am not sure which version of Nagios is embedded.

Which file are you talking about? I have:
commands.cfg which includes many other command definitions thats works.
vmware.cfg which include many other service and host definitions that works.

Only file that i could do a mistake with is the vc.cfg (renamed this not to confuse it with the other file) which includes only these lines:
VI_PASSWORD=<password>
VI_SERVER=<hostname of the vc server>
VI_USERNAME=<domain>\<username>

One thing i am not sure about.. the line "check_command check_vmware!/usr/local/icinga/vc.cfg!cpu!--host="VCENTER01"" in the vmware.cfg file.... the file stated: vc.cfg, that is the file that includes the three lines above with the credentials, right?

Where should the file check_vmware.pl be placed?

I have attached the two files i use.
The third file i cannot attach as it includes the user credentials, but it is the vc.cfg which i reference in "check_command check_vmware!/usr/local/icinga/etc/vc.cfg!cpu!--host="VCENTER01"".

I noticed in your cfg file, you are using the template generic-service for your VMWare:CPU service definition; this is the name of the template we use here, but have you defined a similarly named service template? It seems to me that you may need to change this to match whatever you use as your generic service template, possibly local-service ?

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I changed that as well. Same.

But.. i now installed a new server based purely on Nagios.
I installed everything like you said, and now i got another error: (Return code of 127 is out of bounds - plugin may be missing)

I installed the vSphere SDK, SOAP::Lite and Class::MethodMaker.

The 'return code out of bounds' error means the plugin failed to run for some reason.

Check you can run it form the command line (there may be missing modules)

Check that the Nagios user has read permissions to the appropriate config files, and that it can write to the cache file (this can happen if you run as root then run as nagios; the cache file is created by root and nagios cannot write to it)

Make sure that it is NOT using the EPN (there should be the '# nagsio: -epn' line at the beginning of the script) as the EPN cannot handle the VMWare API perl module correctly.

Check the script has correct permissions etc on it

Check your command definition in Nagios is correct; it may need to explicitly specify the perl executable rather than just the script name. Make sure all paths are absolute, not relative

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

After i runned it from the command line it showed an error. Then i put .pl after the script and it runned.
But now i get another error about the host as seen below.
I tried to switch the hostname with the IP, and it still gave the same error:

./check_vmware.pl --mode=nagios --config=/usr/local/nagios/etc/vc.cfg --report=cpu --host=vcenter01
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server certificate request A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client certificate A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read finished A
UNKNOWN: Host system 'vcenter01' not found.

I verified connectivity, i can ping both the hostname and the ip.

It is searching for this host name in your virtualcentre, not via DNS.

The hostname you specify must match the hostname as specified for the ESX Server within the virtualcentre, which does not necessarily match the hostname... and must match it exactly, capitalisations and all (eg it may be fully qualified hostname in your VC interface)

You also appear to be getting the SSL debug info appearing; this is something odd in the VMWare API that I cannot work out how to stop, and it doesnt happen on our system...

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Spot on, it was a wrong naming.

Thanks for your effort, its working like a charm now

Hi Gents,

I managed to fix the SSL problems, they were due to missing dependencies for the Vmware SDK, detailed here: http://www.vmware.com/support/developer ... nstall.pdf

I can now get valid data returned to the command line perfectly, but in NAGIOS, I still get (Return code of 127 is out of bounds - plugin may be missing).

The exact same command run from the CLI as the nagios user is as follows:
nagios@AU4RLBN012A:/usr/local/nagios/libexec$ ./check_vmware --mode=nagios --mode=nagios --config /usr/local/nagios/etc/objects/vmconfig --report=memory --host=esx1
Memory usage at 54.23%<BR> (No MEM fairness data)|mem=54.23%;80;90;0;100

Any ideas?

If you have Nagios with EPN enabled, try adding a line '#nagios: -epn' as the second line in the script. This will disable using the EPN which may help.

Make sure your checkcommands.cfg is giving the corretc name of the script, with the correct full pathname (maybe a typo in there?)

Also, if you are using a cache file, make sure the Nagios user can write to it (possibly it was created during a test as the root user?) though this is unlikely to be the problem.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11