[pm_lwp_protocol_https 0005258]: pm_lwp_protocol_https tell is installed but not working
Mantis Bug Tracker via bug-notifications
bug-notifications at lists.opencsw.org
Wed Jun 15 15:11:53 CEST 2016
A NOTE has been added to this issue.
======================================================================
https://www.opencsw.org/mantis/view.php?id=5258
======================================================================
Reported By: ggbce
Assigned To: dam
======================================================================
Project: pm_lwp_protocol_https
Issue ID: 5258
Category:
Reproducibility: always
Severity: block
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2015-11-13 22:58 CET
Last Modified: 2016-06-15 15:11 CEST
======================================================================
Summary: pm_lwp_protocol_https tell is installed but not
working
Description:
In very short story, I installed "pm_lwp_protocol_https" required for my
"fi_agent" that report through a GLPI server in https. But I got an error
telling the "lwp protocol https" is not installed. I also tried with a
basic Perl script that call a secure website and I got the same error like
the Perl Module LWP protocol https is not installed.
I installed it by the normal method /opt/csw/bin/pkgutil -y -i
pm_lwp_protocol_https and the setup is done successfully. It's like it
installed... but not really installed (due to missing compilation or loaded
modules Under Perl)
======================================================================
----------------------------------------------------------------------
(0011156) ggbce (reporter) - 2016-06-15 15:11
https://www.opencsw.org/mantis/view.php?id=5258#c11156
----------------------------------------------------------------------
Hi dam,
Thank you for you reply and verification. I tested again with your script
and I got the same error.
I got an access to an another Sun SPARC server to test this same script...
and it work !
Finally, the problem seem to be localized with a specific machine only. You
can close this request.
Regards,
GGBCE
More information about the bug-notifications
mailing list