There appears to be a problem with the following combination: apache version 2.0.54-r7 mod_php version 4.3.11 openldap version 2.1.30-r4 phpldapadmin version 0.9.6c If apache is started with the -D PHP -D LDAP -D AUTH_LDAP phpldapadmin fails to work and the following messages is logged in /var/log/apache2/errors.log: [Thu Jun 30 11:54:48 2005] [notice] child pid 27088 exit signal Aborted (6) *** glibc detected *** corrupted double-linked list: 0xb7c5da7c *** *** glibc detected *** corrupted double-linked list: 0xb7c5da7c *** [Thu Jun 30 11:54:51 2005] [notice] child pid 27089 exit signal Aborted (6) [Thu Jun 30 11:54:51 2005] [notice] child pid 27091 exit signal Aborted (6) *** glibc detected *** corrupted double-linked list: 0xb7c5da7c *** [Thu Jun 30 11:54:53 2005] [notice] child pid 27092 exit signal Aborted (6) *** glibc detected *** corrupted double-linked list: 0xb7c5da7c *** [Thu Jun 30 11:55:06 2005] [notice] child pid 27090 exit signal Aborted (6) *** glibc detected *** corrupted double-linked list: 0x08346740 *** This does seem to work using apache 2.0.52-r1 and mod_php 4.3.10. I need to able to use LDAP_AUTH with phpldapadmin to restrict access to the interface and other website running on the same machine. Right now I'm using pam_ldap nss_ldap and mod_auth_pam as a workaround Reproducible: Always Steps to Reproduce: 1. This showed up after an update 2. use phpldapadmin and apache -D LDAP -D AUTH_LDAP 3. apache child fails Expected Results: allow login and browsing using phpldapdmin
(In reply to comment #0) > There appears to be a problem with the following combination: > apache version 2.0.54-r7 > mod_php version 4.3.11 > openldap version 2.1.30-r4 > phpldapadmin version 0.9.6c > This does seem to work using apache 2.0.52-r1 and mod_php 4.3.10. > I need to able to use LDAP_AUTH with phpldapadmin to restrict access to the > interface and other website running on the same machine. Do you mean that phpldapadmin-0.9.6c works with 2.0.52-r1, but not with 2.0.54-r7? If so, this would be an Apache issue.
Yes, this is a known bug in Apache 2.0.54. It will be fixed in 2.0.55: http://issues.apache.org/bugzilla/show_bug.cgi?id=34618 This bug has already been reported in #94583 *** This bug has been marked as a duplicate of 94583 ***
