Description of problem:
When using openldap tools on Fedora Core 3 test 2 (against an Active
Directory server in my case), lookups hang at ldap_int_select.
The issue has been described, addressed and fixed in a later version
of OpenLDAP (somewhere between 2.2.14 and the current 2.2.17), as
described by the URL above or here:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run an ldapsearch against an LDAP database (my command was
"ldapsearch -d1 -lll -x "sn=hagge")
2. observe hang after ldap_int_select
See http://www.openldap.org/its/index.cgi/Software%20Bugs?id=3192 for
After applying the fix shown at the OpenLDAP URLs, the test was
repeated and was successful. I believe that the final FC3 release
should either incorporate this patch or (better) use a more up-to-date
version of OpenLDAP (eg. 2.2.17) which has this patch incorporated.
I ran into this exact problem myself. I've spent a good portion of
this weekend creating openldap-2.2.17 RPMs (each build took 45 minutes
on my machine) for FC2... they should work the same on FC3. (Right?)
It'd be great if openldap-2.2.17 could see it's way into either FC2
updates or FC3 final!
In the meantime, if you'd like to test drive the RPMs I've build,
please give them a shot.
Basically, I took the 2.1.17 spec file and made very minor changes to
it to get it to build against 2.2.17 source. I needed to redo some of
the patch files, and it would only build if I installed the db4 and
db4-devel packages on my system (it wouldn't compile 2.2.17 with the
db4 source included with the SRPM for 2.1.17)... but it works great
and doesn't suffer from the ITS#3192 SASL hang bug.
Created attachment 109465 [details]
patch to fix hang
You can also apply this patch to 2.2.13 (from the linked bug report).
I built new packages with this patch and they work and fix the problem.
Rawhide contains 2.2.23, which contains an equivalent change; removing
from FC4 tracker.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
This was fixed for FC4 and up. Closing, since FC3 is only supported for
critical security updates.