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

Re: LDAP API problems (possible duplicate)

I failed to leave out one important
detail: this all works perfectly using the 1.2.7 API.
The server logs report 'TCP connection reset by peer'
which makes me think the client is terminating the
connection for some reason.  Relevant trace output
the ldapsearch execution is below along with server
entries for the query:

** Outstanding Requests:
 * msgid 2,  origid 2, status InProgress
   outstanding referrals 0, parent count 0
** Response Queue:
sockbuf_read: want=1, got=1
sockbuf_read: want=1, got=1
sockbuf_read: want=3, got=3
        03  B f0 
ber_get_next failed.
ldap_result: Can't contact LDAP server
ldap_free_request (origid 2, msgid 2)

Server logs:

[05/Oct/2000:10:37:39 -0700] conn=71 op=0 BIND dn=""
method=128 version=3
[05/Oct/2000:10:37:39 -0700] conn=71 op=0 RESULT err=0
tag=97 nentries=0 etime=0
[05/Oct/2000:10:37:40 -0700] conn=71 op=1 SRCH
base="o=jpctest.com" scope=1 filter="(cn=test_object)"
[05/Oct/2000:10:37:40 -0700] conn=71 op=1 fd=41 closed
error -5961 (TCP connection reset by peer.) - B4
[05/Oct/2000:10:37:40 -0700] conn=71 op=-1 fd=41
error 9 (Bad file number) - B1

Thanks again,  Jeff Carter

--- "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> wrote:
> At 01:34 PM 10/4/00 -0700, Jeffrey P. Carter wrote:
> >I apologize if this is a duplicate message, but I
> >don't see my previous message in the archive.
> Give the cron job a chance to run...
> >I'm having problems with ldap_search_s() in the
> >2.0.4 API.  I'm using Netscape's 4.11 LDAP server
> and
> >when I try to get large attribute values out of the
> >directory, the ldap_search_s call fails and returns
> Check the server logs for details.
> >This despite the fact that
> to
> >LDAP_NO_LIMIT using the ldap_set_option() call.
> Server may enforce restrictions beyond those
> requested
> by the client.  However, the result code
> is meant to be returned with the result set contains
> too
> many entries regardless of number of attributes,
> values, and
> their sizes or combined size.
> >I
> >have no problems when I search for an attribute
> with
> >a small value like cn.  The value I'm trying to
> get,
> >though, is around 1MB.  I haven't yet established
> >what the "cutoff" might be.
> >Further, this problem can also be duplicated using
> the
> >ldapsearch command-line tool.  I'm certain I'm not
> >getting a referral back and that only a single
> entry
> >is being returned by the search.  With the debug
> level
> >set at 255 on the ldapsearch tool, it reports that
> >ber_get_next failed.
> A ber_get_next failure is not necessarily an error.
> Details?
> >I was wondering if this is a known problem and if
> >there is a workaround?
> The obvious work around is "don't do that"...
> Kurt

Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!