That would mean that the API is OK, but the problem lies in the security rules on the ESX server (or VC server)
Statistics: Posted by stevesh — Fri Jun 24, 2011 12:28 pm
]]>
]]>
i added the line to my script, but i don't want to test it now
never touch a running system 
Statistics: Posted by smg72523889 — Wed Jun 22, 2011 3:25 am
]]>
$ENV{PERL_LWP_SSL_VERIFY_HOSTNAME} = 0;
Franky
Statistics: Posted by liedekef — Wed Jun 22, 2011 3:20 am
]]>
We use the latest 4.1 SDK (I think) with Perl 5.10 and the latest VirtualCentre.
Steve
Statistics: Posted by stevesh — Thu Jun 16, 2011 11:16 am
]]>
i think the problem could be situated in vmware's perl sdk using deprecated functions?
maybe a new version of sdk will work ... i'm waiting - and next time i'll test it before installing updates
Statistics: Posted by smg72523889 — Wed Jun 15, 2011 9:59 pm
]]>
I had already checked my vmware servers and the virtualcentre server. The API is available, because i'm able to access it with an older nagios installation.
I couldn't solve the problem and had not enough time to test any further so i had to go back to an older backup-image.
Similar to smg72523889, the poblem started when i made an update of the whole system (debian) including perl...
if i have new information i'll post it.
Statistics: Posted by rhartbrich — Wed Jun 08, 2011 9:08 pm
]]>
i get the same message and i think it happens since a system-update of my monitoring-server running suse11.4 -> but i don't know where to start searching 4 solution
i can replicate it by updating my fedora14 and gets the same message.
could there be a significant change in perl-installation conflicting with vmware-perl-api?
there was no change on virtualcenter & esx-servers.
today i'll try to downgrade my perl-version, hope it works...
Statistics: Posted by smg72523889 — Wed Jun 08, 2011 8:47 pm
]]>
Check the installation on the vmware server -- make sure the API is available, and you have the firewall open appropriately (this is what I think is most likely the issue). I usually access the API on the virtualcentre, not on the vmware server itself.
Statistics: Posted by stevesh — Tue May 17, 2011 2:59 pm
]]>
Since we updated our VMware servers i have a problem with the check_vmware.pl plugin.
I used the plugin to monitor our VMware servers through the vCenter api.
When i execute the command:
perl check_vmware.pl -config=vmconfig -report=cpu
i get the following error:
UNKNOWN: Login to VirtualCentre server failed: Server version unavailable at 'https://192.168.88.183:443/sdk/vimService.wsdl' at /usr/local/share/perl/5.10.0/VMware/VICommon.pm line 545.
The config file:
VI_PASSWORD=xxxxxx
VI_SERVER=192.168.88.183
VI_USERNAME=<user>
Versions:
check_vmware.pl --version
vSphere SDK for Perl version: 4.1
Script 'check_vmware.pl' version: 1.13
Nagios Version: 3.2.1
vSphere Client 4.1.0
VMware vCenter Server 4.1.0 Build 258902
ESX Servers: 4.1.0 348481
The following modules are installed:
apt-get install libxml2-dev # bei Debian
apt-get install libssl-dev
cpan Crypt::SSLeay
cpan SOAP::Lite
cpan Class::MethodMaker
cpan Data::UUID
cpan -r // recompile perl modules
cpan XML::LibXML
---------------------------- VMware vSphere SDK ---------
VMware-vSphere-Perl-SDK-4.1.0-254719.i386.tar.gz (unpacked, compiled and installed)
I hope you are able to help me.
Thanks in advance,
Rolf
Statistics: Posted by rhartbrich — Thu May 12, 2011 10:44 pm
]]>