in reply to 501 Attempt to reload IO/Socket/SSL.pm aborted.

The error message contains "LWP::Protocol::https not installed" - I would pursure that avenue.

How did you make sure that for your new version of Perl, LWP::Protocol::https is actually installed?

  • Comment on Re: 501 Attempt to reload IO/Socket/SSL.pm aborted.

Replies are listed 'Best First'.
Re^2: 501 Attempt to reload IO/Socket/SSL.pm aborted.
by haj (Vicar) on Aug 03, 2018 at 13:37 UTC
    As far as I recall, LWP::Protocol::https has always been bundled with Strawberry Perl (for details see Release Notes). With all the symptoms provided, I guess there's an issue with an openssl library. Strawberry Perl comes bundled with its own which should work quite fine, but perhaps the build procedures find another, incompatible version? An older one perhaps, lingering around from the old Perl version, which can't be replaced because the file is in use?
[reply]

      Your guess is correct. It didn't have the openssl dll's for some reason and there doesn't seem to be anything Strawberry specific it approves. I extracted the Strawberry's web site's libssl and libcrypto to their respective folders perl\c\bin, but it didn't still find them and I don't know why it doesn't look in there. I copied them to \Strawberry\perl\vendor\lib\auto\Crypt\SSLeay to test if they work at all and after that I got at least a different error 

      Net::SSL from Crypt-SSLeay can't verify hostnames; either install IO::
+Socket::SSL or turn off verification by setting the PERL_LWP_SSL_VERI
+FY_HOSTNAME environment variable to 0 at /STRAWBERRY/perl/site/lib/LW
+P/Protocol/http.pm line 50.

      [download]

      If I remember correctly, this happens because Crypt-SSLeay doesn't support hostname verification, but instead I should use IO::Socket:SSL as the error message also tells? And I'm probably doing something wrong with the dll's, since they cannot be found.

      Edit: I could add use IO::Socket::SSL to the beginning of the code, but earlier it used that module automatically, so I suspect it just tries Crypt-SSLeay as the first one doesn't seem to work.

      Edit2: There are actually two Perl's on that server and just the first (older) has its c\bin in path. Might affect the finding of the dll's. <facepalm>

[reply]
[d/l]

        I seem to recall that indeed LWP tries IO::Socket::SSL first, and if this fails, tries to use Crypt::SSLeay directly.

        But as already mentioned, Strawberry usually comes with all the libraries it needs if you either install the .msi file or the portable edition. The latter helps a lot if you want to run different versions of Strawberry perl on your system, otherwise, the library paths will most likely get mixed up.

        In my installation (portable, 5.26.2.1, 64bit) I have a c\bin\libssl-1_1-x64__.dll and ...libcrypto-1_1-x64__.dll as OpenSSL libraries, plus a bunch of Perl wrapper DLLs in perl\vendor\lib\auto\Crypt\OpenSSL\* plus perl\vendor\lib\auto\Crypt\SSLeay.xs.dll. Maybe the road to success is just to re-install Strawberry?

[reply]

In Section Seekers of Perl Wisdom