vEMan_v0.9.6/vmapps/general# ./connect.pl --server 192.168.x.x
Enter username: root
Enter password:
Server version unavailable at 'https://192.168.x.x:443/sdk/vimService.wsdl' at /usr/share/perl/5.20/VMware/VICommon.pm line 545, <STDIN> line 2.
this error indicates a problem with the damn (sorry) Perl SDK. The reasons varies but normally there is something missing or went wrong regarding the installation of the SDK.
Please re-install the SDK and keep an eye at the last messages!! This is very important because even when it looks like there was noerror the installer sometimes states that it misses some perl modules. Those modules need to be installed manually when the SDK installer is not able to do so. If you like paste the whole output of the installation at http://pastebin.com/ and link it here.
when it comes to a manual perl module installation try to "apt-cache search modulename" first. In most cases there are Ubuntu packages available.
Last edit: secure diversITy 2016-03-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I realise this thread is from 4 years ago, however I'm having the same issue, and can't find any other references to this issue.
I think my cause may be different however, as I can retrieve the vimService.wsdl file manually, and it doesn't contain anything that looks like a version (to me anyway), eg:
Talking to myself possibly, however, I did find the cause of and solution to this issue.
The newer perl LWP/https stuff forces cert verification, and our servers don't have legit certs, just the "VMware ESX Server Default Certificate".
My fix was to modify /usr/share/perl5/LWP/Protocol/https.pm
unable to access to ESXi 5.0.0
Distro: Ubuntu 15.04 64bit
Hi claenjoy,
this error indicates a problem with the damn (sorry) Perl SDK. The reasons varies but normally there is something missing or went wrong regarding the installation of the SDK.
Please re-install the SDK and keep an eye at the last messages!! This is very important because even when it looks like there was no error the installer sometimes states that it misses some perl modules. Those modules need to be installed manually when the SDK installer is not able to do so. If you like paste the whole output of the installation at http://pastebin.com/ and link it here.
when it comes to a manual perl module installation try to "apt-cache search modulename" first. In most cases there are Ubuntu packages available.
Last edit: secure diversITy 2016-03-16
I realise this thread is from 4 years ago, however I'm having the same issue, and can't find any other references to this issue.
I think my cause may be different however, as I can retrieve the vimService.wsdl file manually, and it doesn't contain anything that looks like a version (to me anyway), eg:
This is from "HP Customized Image ESXi 5.5.0 version 5.71.3 based on ESXi 5.5.0 Vmkernel Release Build 1331820."
I think I have all the perl stuff installed correctly, but perhaps, as I did have to wrestle with some dpkg and pip3 files/commands..
Talking to myself possibly, however, I did find the cause of and solution to this issue.
The newer perl LWP/https stuff forces cert verification, and our servers don't have legit certs, just the "VMware ESX Server Default Certificate".
My fix was to modify /usr/share/perl5/LWP/Protocol/https.pm
in the top of the file, I found:
I added below this:
So it now accepts the invalid cert.
Can connect, but trying to connect to the console of any VM doesn't work, but that's a different issue.
thx for reporting !
tbh did not expect anyone uses this anymore ;)