Installing the VMware vSphere Command Line Interface (CLI) has the potential for problems. In my case, it generated an error – a three-year old error. Perl returns the error:
undefined symbol: Perl_Tstack_sp_ptr
Not only has this error been around for three years, it also has shown up in numerous other instances. Ed Haletky wrestled with the error in VMware vSphere CLI back in June of 2008. The error surfaced in Arch Linux in 2008, both in running their package manager and in running cpan itself. This error also came up (again in 2008) in attempting to build and run Zimbra. (The response from Zimbra support was cold and unwavering: we don’t support that environment and won’t discuss it. How unfortunate.) The error also affected the installation of Bugzilla according to this email thread from 2009.
On the Perl Porters mailing list, there is an in-depth response as to what causes this error. From reading these messages, it appears that there are two related causes:
- Using modules compiled for Perl 5.8 with Perl 5.10
- Using modules compiled against a threaded Perl with an unthreaded Perl
One recommended solution is to recompile the modules using the cpan utility:
That may or may not be enough; it depends on if there were other errors. In attempting to run the vSphere CLI, I get this error:
IO::Compress::Gzip version 2.02 required--this is only version 2.005
To fix this, I ran cpan this way:
In my case, that loaded IO::Compress::Gzip version 2.033.
I also loaded the libxml2-dev package; I don’t know if that was necessary or not:
apt-get install libxml2-dev
Whenever using cpan, I always wonder how it affects my packaged installations and whether it installs for all users or just me (and how to control that) – but I’ve never had any problems and installs as root seem to go into /usr/local – which makes sense.
Having done all this, I can now use the vSphere CLI to activate SNMP on the ESXi 4 servers. For the record, this is an integral part of ESXi 4 and supports all SNMP polling and traps – previously, only SNMP traps were supported. Certainly a nice improvement.
2 thoughts on “Installing VMware vSphere CLI 4.0 in Ubuntu 10.04 LTS”
After searching high and low to this issue thank you for this post it solved my issue.
Thank you for this!!!! Very helpful.