ESX Wizard

[Koobal]

Yes I can, but after a certificate warning.
I have the same warning on ESX wich are ok...
It's just weird...

[mguthrie]

Definitely weird. From what I'm reading the self-signed certificate is viewed as a fatal error by some perl modules, but what makes this really weird is that it's working on some of your servers and not others. I came across this thread with the same error message.
http://www.steveshipway.org/forum/viewt ... =28&t=4332

Another forum also mentioned adding this environment variable to the check script right after the first line:

Code: Select all

$ENV{SSL_verify_mode} = 0x00;

But that had mixed results. You could also try reinstalling the vmware sdk and see if that makes any difference.

Also came across this on Vmware's release notes:
http://www.vmware.com/support/developer ... notes.html

When you run a vicfg- vCLI command, an error like the following might result.
Server version unavailable at 'https://<server>/sdk/vimService.wsdl' at /usr/lib/perl5/5.8.8/VMware/VICommon.pm line 545

Workaround: Follow these steps to resolve the issue:

Make sure the version of the LWP::UserAgent Perl module is above 6.0.4.
Turn off host name verification by running the following command:
export PERL_LWP_SSL_VERIFY_HOSTNAME=0

[Koobal]

I sorry, for the delay.
Here is one another weird thing about this problem.
When i take a look in my state history report i have the following :

statusESX.JPG

The service is flapping but with this error Host IO or CPU unknown...

[scottwilkerson]

This could be caused by you losing connectivity to the ESX server during this timeframe or the servers API not responding in a timely manner.

[Mt6uo]

By adding

Code: Select all

$ENV{'PERL_LWP_SSL_VERIFY_HOSTNAME'} = 0;

at the top of my check_esx3.pl script I fixed the error

Code: Select all

Server version unavailable at 'https://<server>/sdk/vimService.wsdl' at /usr/lib/perl5/5.8.8/VMware/VICommon.pm line 545