Since I upgraded httpd from 2.0.53 to 2.0.54, I have frequently segmentation faults (redhat 7.3). My httpd execute libphp4.so. If I run this little script php, I generate the problem systematically : for($i=0;$i<1000;$i++){ $l = ldap_connect("ldap.univ.fr"); } (ldap.univ.fr doesn't exists). If I compile httpd-2.0.54 with util_ldap.c from httpd-2.0.53 version, the problem disappear
*** Bug 34620 has been marked as a duplicate of this bug. ***
Brad Nicholes requested that someone test this patch: http://svn.apache.org/viewcvs/httpd/httpd/trunk/modules/ldap/util_ldap.c?rev=164919&r1=164918&r2=164919&view=diff
(In reply to comment #2) > Brad Nicholes requested that someone test this patch: > > http://svn.apache.org/viewcvs/httpd/httpd/trunk/modules/ldap/util_ldap.c?rev=164919&r1=164918&r2=164919&view=diff I try to execute this patch (with 2.0.54 util_ldap.c). I have an error during patch executing : File to patch: util_ldap.c patching file util_ldap.c Hunk #1 FAILED at 247. Hunk #2 succeeded at 321 (offset -9 lines). Hunk #3 FAILED at 1784. Hunk #4 FAILED at 1917. 3 out of 4 hunks FAILED -- saving rejects to file util_ldap.c.rej
Brad, can you provide a patch which applies to 2.0.x which mod_ldap users can test?
Created attachment 14873 [details] switch to connection timout per ldap connection Test the ldap connection timeout on a per connection basis rather than global
(In reply to comment #5) > Created an attachment (id=14873) [edit] Good! I compiled apache2.0.54 with your patch. I do not have any more segmentation faults Thank's
Created backport proposal in the STATUS file. Just waiting for the three +1 votes.
*** Bug 34705 has been marked as a duplicate of this bug. ***
I installed the patch and compiled it, and at first it seemed to work. But I do some tests, works, and then if some time passes from the last test and I make a new one, the apache process hangs. I think that the ldap connection pool has some issues with the connection timeouts and that makes the apache process to be unresponsive,
The patch has been backported to 2.0.55-dev
i tried the patch with apache 2.0.54 and recompiled. I still getseg faults in the error log [Tue Jul 12 11:57:52 2005] [notice] child pid 24029 exit signal Aborted (6) [Tue Jul 12 11:57:54 2005] [notice] child pid 23956 exit signal Segmentation fault (11) any ideas
I tried the patch on a LDAP enabled apache-2.0.54 on SuSE Enterprise Linux 9 but get more segmentation faults afterwards. This apache was compiled against the builtin openldap 2.2.6 in SLES9. After installation of openldap-2.2.27 and recompilation of apache against this version the segmentation faults are gone. This seems to be related to the following patch in openldap 2.2.20 http://www.openldap.org/its/index.cgi/Software%20Bugs? id=3487;expression=TIMEOUT;casesensitive=1;usearchives=1;statetype=-1
We also applied the patch to 2.0.54 and the segmentation fault errors appeared again, although less frequent. I see there was a bug fixed in openldap, we use mod_ldap and auth_ldap, should we be using openldap?
Yes, you need to update OpenLDAP (In reply to comment #13) > We also applied the patch to 2.0.54 and the segmentation fault errors appeared > again, although less frequent. I see there was a bug fixed in openldap, we use > mod_ldap and auth_ldap, should we be using openldap?
We are having the same problem with Microsoft Active Directory Service (Windows 2000), we don't use OpenLDAP. We did the patch on 2.0.54 but didn't help. So we're looking for a Windows 2000 bug now? Is this bug closed because it works with OpenLDAP server? Can anyone else test on Windows 2000? (In reply to comment #14) > Yes, you need to update OpenLDAP > (In reply to comment #13) > > We also applied the patch to 2.0.54 and the segmentation fault errors > appeared > > again, although less frequent. I see there was a bug fixed in openldap, we > use > > mod_ldap and auth_ldap, should we be using openldap?
Broughan, this bug concerns a specific issue with OpenLDAP introduced in 2.0.54 which is now fixed for 2.0.55. Bug 18334 seems to be a generic "problems with Microsoft LDAP SDK" bug.