[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: openldap libraries & filters

To: Lieuwe Elgersma <lieuwe.elgersma@gmail.com>
Subject: Re: openldap libraries & filters
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Wed, 21 Dec 2005 10:07:37 -0800
Cc: OpenLDAP-software@OpenLDAP.org
In-reply-to: <2dfb09e0512210932h2a0d27abh179484a3bf7dd8f8@mail.gmail.com >
References: <2dfb09e0512210516x768ae302iacc0e4c8a801ad44@mail.gmail.com> <6.2.1.2.0.20051221090700.0313c530@mail.openldap.org> <2dfb09e0512210932h2a0d27abh179484a3bf7dd8f8@mail.gmail.com>

At 09:32 AM 12/21/2005, Lieuwe Elgersma wrote:
>>
>> It's not clear to me what code you mean here.  And though
>> you describe the error as coming from the library, it's
>> not clear to me wether the error is an "API" error or
>> a "Protocol" error.  What is the precise error code?
>> Was any error text provided?  If so, what was it?
>>
>> Kurt
>>
>>
>
>Sorry I should have been more precise ... the ldap_search_s returns with an
>LDAP_OTHER ("Internal (implementation specific) error")  when the
>filter I described contains more then a certain number of sections.

Okay, this is a protocol error, not an API error.  That is,
it's provided by the server.  Note the error string you
quote is API generated.  There may also be server provided
error text.  This may help you narrow the problem.

However, as Ando and others have noted, the problem is
likely that server is refusing to process the overly
large request.

You can likely confirm this by examining the server's
logs.

Kurt

References:
- openldap libraries & filters
  - From: Lieuwe Elgersma <lieuwe.elgersma@gmail.com>
- Re: openldap libraries & filters
  - From: Lieuwe Elgersma <lieuwe.elgersma@gmail.com>

Prev by Date: Re: Meta to Ldap loopback not working.
Next by Date: Re: openldap libraries & filters
Index(es):
- Chronological
- Thread