Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plugins error #201

Closed
erpiu72 opened this issue Sep 30, 2022 · 2 comments
Closed

plugins error #201

erpiu72 opened this issue Sep 30, 2022 · 2 comments

Comments

@erpiu72
Copy link

erpiu72 commented Sep 30, 2022

Good morning

I installed the plugins on a centos 8 with sdk 6.5 and all its components, I verified that all the perl components were present and despite this it continues to give me this error.

Use of uninitialized value in lc at /usr/lib64/perl5/libwww-perl-5.837/lib/HTTP/Cookies.pm line 573.
Server version unavailable at 'https://localhost:443/sdk/vimService.wsdl' at /usr/share/perl5/VMware/VICommon.pm line 734.

@erpiu72
Copy link
Author

erpiu72 commented Oct 8, 2022

searching on the internet i found some articles now i came to this message

/usr/bin/perl: symbol lookup error: /usr/lib64/perl5/auto/MIME/Base64/Base64.so: undefined symbol: Perl_Istack_sp_ptr

@BaldMansMojo
Copy link
Owner

Hi,
errors like this are normally not caused by plugin. It's caused by libwww-perl. Or the SDK itself. According to your message it's caused by your VMWare installation. The server version is not delivered by your ESX host to the SDK. So first try with command line tools.

See:
https://www.google.de/search?q=vmware+perl+sdk+server+version+unavailable&source=hp&ei=FWZBY_iLGrmSxc8Pk-OEmA4&iflsig=AJiK0e8AAAAAY0F0JaJ9YU0TdXKpVKZaeFT2m7O7idaS&ved=0ahUKEwi46rG_ytD6AhU5SfEDHZMxAeMQ4dUDCAg&uact=5&oq=vmware+perl+sdk+server+version+unavailable&gs_lcp=Cgdnd3Mtd2l6EAMyBggAEB4QFlDyBljyBmCiCmgBcAB4AIABaIgBaJIBAzAuMZgBAKABAqABAbABAA&sclient=gws-wiz

and

https://community.spiceworks.com/topic/458264-nagios-check_vmware_api-pl-server-version-unavailable

This is not a plugin error. Therefore I close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants