Andrew Bartlett wrote:

On Tue, 2007-12-11 at 14:22 -0800, Howard Chu wrote:

...

Andrew Bartlett wrote:

...

I wonder if there is a known issue with db 4.6 and OpenLDAP, as Fedora's OpenLDAP seems to include it's own libslapd_db-4.4.so (it has a slapd_db_stat to match, for 4.4).

I think they packaged that to avoid using BDB 4.3 which was known to be broken. I've been using OpenLDAP with BDB 4.6.1 thru 4.6.3, and 4.6.18 thru 4.6.21 without any trouble.

Where there any further clues on my deadlock in the db_stat output?

I've just built Samba4 from svn and tried to run this test, but it fails much earlier on my AMD64 system. It looks like your ldbsearch client is generating an invalid request, perhaps it's not 64-bit aware.

In st/dc/private/ldap/logs I see:

...

...

slap_listener(ldapi://%2Fhome%2Fsoftware%2FSAMBA_4_0%2Fsource%2Fst%2Fdc%2Fprivate%2Fldap%2Fldapi) daemon: activity on 1 descriptor daemon: activity on: daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: listen=7, new connection on 20 daemon: activity on 1 descriptor daemon: activity on: 20r daemon: read active on 20 daemon: added 20r (active) listener=(nil) daemon: epoll: listen=7 active_threads=0 tvp=NULL connection_get(20) connection_get(20): got connid=0 connection_read(20): checking for input on id=0 ber_get_next ldap_read: want=8, got=8 0000: 80 04 00 0a 01 00 0a 01 ........ ber_get_next on fd 20 failed errno=34 (Numerical result out of range) connection_read(20): input error=-2 id=0, closing.

All LDAP requests should begin with 0x30, the BER Sequence tag.