httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Poggenpohl, Daniel" <daniel.poggenp...@fernuni-hagen.de>
Subject AW: [users@httpd] Can't activate LDAPS support in my OpenSSL 1.0.2g/OpenLDAP 2.4.44/Apache 2.4.18/PHP 5.6.20 combination
Date Fri, 15 Apr 2016 11:22:13 GMT
Hello again,

after fixing the rpaths in my binaries/libraries for Postgres and the curl that was used during
runtime (prepended /moodle/openssl/latest/lib), which wasn't /usr/bin/curl, but /usr/local/bin/curl...
I could finally remove the OpenSSL path from LD_LIBRARY_PATH.

Doing the same with OpenLDAP however doesn't work because all involved binaries and libraries
(php, libphp5.so, curl, libcurl, ...) point to libldap.so.5 (which seems to be Solaris specific).
When I put a softlink in my OpenLDAP libs dir libldap.so.5 ->libldap.so and ldd the binaries,
the found library doesn't contain the defined Solaris SUNW5_1 interface definition, so I'd
rather not use something that produces such errors/warnings.
So the next step is to try to make both programs point to OpenLDAP 2.4.44 instead of Solaris
libldap.so.5 ...which, as far as I know, only works by recompiling.

Any thoughts?

Regards,
Daniel P.


-----Ursprüngliche Nachricht-----
Von: Poggenpohl, Daniel [mailto:daniel.poggenpohl@fernuni-hagen.de] 
Gesendet: Freitag, 15. April 2016 08:53
An: users@httpd.apache.org; users@httpd.apache.org
Betreff: AW: [users@httpd] Can't activate LDAPS support in my OpenSSL 1.0.2g/OpenLDAP 2.4.44/Apache
2.4.18/PHP 5.6.20 combination

Good Morning,

thanks, I will try out what you people have suggested. Will report back, hopefully...

Regards,
Daniel P.

-----Ursprüngliche Nachricht-----
Von: Rainer Jung [mailto:rainer.jung@kippdata.de] 
Gesendet: Donnerstag, 14. April 2016 21:04
An: users@httpd.apache.org
Betreff: Re: [users@httpd] Can't activate LDAPS support in my OpenSSL 1.0.2g/OpenLDAP 2.4.44/Apache
2.4.18/PHP 5.6.20 combination

Am 14.04.2016 um 20:51 schrieb Rainer Jung:
> Am 14.04.2016 um 20:39 schrieb Poggenpohl, Daniel:
>> Hello,
>>
>> I just realized that this may not be the problem, but the plugin
>> architecture is. I would have to check all modules in Apache and all
>> extensions in PHP for dependencies to see all involved dependencies,
>> wouldn't I?
>
> On Solaris "pldd" is your friend. It works on a running process, so also
> shows shared objects loaded programattically via dlopen() etc. like
> Apache modules or PHP extensions.

And yet another debug attempt is looking at "man ld.so.1", setting 
LD_DEBUG. The possible settings can be seen by running e.g.

LD_DEBUG=help ANYCOMMAND

in any shell that supports that way of setting an env var for a command 
(like sh or ksh) and ANYCOMMAND can be anything that is not a shell 
builtin (e.g. you can use again "sh").

Symbol resolution should be trackable with LD_DEBUG=symbols, but it will 
give LOTS of output. Probably it helps to start Apache in single process 
mode (-X). The output of the debug flag can be written to a file whose 
name is given by the LD_DEBUG_OUTPUT env var (again see "man ld.so.1").

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[
�\�\��][��X��ܚX�P
�\X�K�ܙ�B��܈Y][ۘ[��[X[��K[XZ[
�\�\��Z[
�\X�K�ܙ�B
Mime
View raw message