Re: (ITS#5504) ldapsearch hangs retrieving info

[quanah@zimbra.com]

--On Wednesday, May 14, 2008 9:56 AM +0000 Javier.Fernandez@cern.ch wrote:

>    unfortunately there?s no update for openladp under SL4, that?s why we
> are using such version. In fact I see no newer versions but for Fedora
> and Mandriva


<http://staff.telkomsa.net/packages/>
or
<http://www.symas.com>

>    In fact, other sites are living nice with that version or older ones.
> In any case, I have compiled and built latest stable version from
> openldap project webpage (2.3.39) and I get the same problem. I'm not
> saying this is a bug from ldap, but something with local area network
> configuration.
>
>    I'm asking for some support to debug this problem actually.

If the bug is not specifically in the OpenLDAP software, I suggest you 
peruse:

<http://www.openldap.org/support/>

I would note I don't see anything particular in what you provide indicating 
the problem is with ldapsearch.  What version of OpenLDAP is the server in 
question running (I see it is OpenLDAP by querying its rootDSE)?

I'll note that a *limited* ldapsearch works just fine:

[quanah@freelancer ~]$ ldapsearch -x -H ldap://exp-bdii.cern.ch:2170 -b "" 
-s base +
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: +
#

#
dn:
structuralObjectClass: OpenLDAProotDSE
namingContexts: o=grid
supportedControl: 2.16.840.1.113730.3.4.18
supportedControl: 2.16.840.1.113730.3.4.2
supportedControl: 1.3.6.1.4.1.4203.1.10.1
supportedControl: 1.2.840.113556.1.4.1413
supportedControl: 1.2.840.113556.1.4.1339
supportedControl: 1.2.840.113556.1.4.319
supportedControl: 1.2.826.0.1.334810.2.3
supportedExtension: 1.3.6.1.4.1.1466.20037
supportedExtension: 1.3.6.1.4.1.4203.1.11.1
supportedExtension: 1.3.6.1.4.1.4203.1.11.3
supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
supportedLDAPVersion: 2
supportedLDAPVersion: 3
supportedSASLMechanisms: DIGEST-MD5
supportedSASLMechanisms: CRAM-MD5
subschemaSubentry: cn=Subschema

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1
[quanah@freelancer ~]$


I would also note that for me, doing a dump of the entire server works just 
fine:

ldapsearch -x -H ldap://exp-bdii.cern.ch:2170 -b "o=grid"

results in:

# search result
search: 2
result: 0 Success

# numResponses: 43962
# numEntries: 43961



Adding -d -1 to the query, I eventually see the same thing you do:

ber_get_next failed.
wait4msg continue ld 0x233f0e0 msgid -1 all 0
** ld 0x233f0e0 Connections:
* host: exp-bdii.cern.ch  port: 2170  (default)
  refcnt: 2  status: Connected
  last used: Wed May 14 09:34:06 2008

** ld 0x233f0e0 Outstanding Requests:
 * msgid 2,  origid 2, status InProgress
   outstanding referrals 0, parent count 0
** ld 0x233f0e0 Response Queue:
   Empty
ldap_chkResponseList ld 0x233f0e0 msgid -1 all 0
ldap_chkResponseList returns ld 0x233f0e0 NULL
ldap_int_select
read1msg: ld 0x233f0e0 msgid -1 all 0
ber_get_next
ldap_read: want=1142, got=0

ber_get_next failed.
ldap_perror
ldap_result: Can't contact LDAP server (-1)
ldap_free_request (origid 2, msgid 2)
ldap_free_connection 1 1
ldap_send_unbind
ber_flush: 7 bytes to sd 3
  0000:  30 05 02 01 03 42 00                               0....B.
ldap_write: want=7, written=7
  0000:  30 05 02 01 03 42 00                               0....B.
ldap_free_connection: actually freed

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration