Nagios Support Forum

Try it as MYCOMPANY\ Cluster (that's a backslash and then the space).

It stills give me an error when I apply, telling : Configuration verification failed.

stkol76,
Use the apostrophe around 'MYCOMPANY Cluster'.

./check_vmware.pl --config=/usr/local/nagios/libexec/check_vmware_config_vcenter01 --mode=nagios --report=cluster --cluster='MYCOMPANY Cluster'

If you type 'MYCOMPANY Cluster' when in the wizard the wizard will mistakenly add the apostrophes to the service description field and this causes the error that the settings could not be applied.

Simply go into Core Configuration Manager and edit the service and remove the apostrophes from the service description field and then apply it. All should be OK then.

I'll add this problem to the list of things to fix in the VMware ESX / vSphere / vCenter Monitoring Wizard.

Did Box293's suggestion work for you?

Hi,

We suddenly started experiencing the same issue. It is not clear if the issue appeared after an upgrade to nagios2011 to whether it started before. In either case the only change has been the upgrade from nagios 2009 to 2011.

When we run any check_vmware.pl service we receive the following error:

./check_vmware.pl --config /usr/local/nagios/libexec/check_vmware_config_vcenter01 --guest <guestname>

UNKNOWN: Login to VirtualCentre server failed: Server version unavailable at 'https://<vcentername>:443/sdk/vimService.wsdl' at /usr/lib/perl5/site_perl/5.8.8/VMware/VICommon.pm line 545.

We restarted the vmware webservices service on the vcenter server but this did not fix our issue. Accessing the following https://<vecentername>:443/sdk/vimService.wsdl provides the following output:

−
<!--

Copyright 2005-2010 VMware, Inc. All rights reserved.
-->
−
<definitions targetNamespace="urn:vim25Service">
<import location="vim.wsdl" namespace="urn:vim25"/>
−
<service name="VimService">
−
<port binding="interface:VimBinding" name="VimPort">
<soap:address location="https://localhost/sdk/vimService"/>
</port>
</service>
</definitions>

Anyone know what could be going on?

Regards,

Hi mariusp,
I've just done a test with a fresh Nagios XI 2011R1.1 VM and all seems OK.

I installed the VMware SDK VMware-vSphere-Perl-SDK-4.1.0-254719.i386.tar.gz.

I performed a simple test at the command line just like your example:

./check_vmware.pl --config /usr/local/nagios/libexec/check_vmware_config_vcenter01 --guest TEST-XP
No alarms detected.

Some things you could try:

• A full reboot of the VMware vCenter Server
  A full reboot of the Nagios XI VM
  Run up a temporary Nagios XI VM and test from there, this will rule out either your Nagios server or your vCenter server

Thanks! Unfortunately it was a very stupid problem: DNS. We changed the NIC and ran dhclient at one point which modified our /etc/resolv.conf. Lame, I know ..
Thanks again,
Marius

Thanks for the update Marius, feel free to contact us again if you have any questions or issues.