Re: LDAP API problems (possible duplicate)

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

This looks like a -lber bug...  I'll see if I can find
and fix the problem...

At 02:55 PM 10/10/00 -0700, Jeffrey P. Carter wrote:
>Thanks.  I forgot to mention in my previous email that
>I don't have this problem when using the 1.2.7 API. 
>I've enclosed more information about the problem this
>time around in the form of relevant server and client
>debug output, below.  I also noticed there'd been some
>changes to the API libs in 2.0.6, but the problem
>still
>exists there as well.  Thanks again for any help.
>
>
>Server log:
>[10/Oct/2000:14:45:16 -0700] conn=14 op=0 BIND dn=""
>method=128 version=3
>[10/Oct/2000:14:45:16 -0700] conn=14 op=0 RESULT err=0
>tag=97 nentries=0 etime=0
>[10/Oct/2000:14:45:16 -0700] conn=14 op=1 SRCH
>base="o=test.com" scope=1 filter="(cn=test_obj)"
>[10/Oct/2000:14:45:16 -0700] conn=14 op=2 UNBIND
>[10/Oct/2000:14:45:16 -0700] conn=14 op=2 fd=32 closed
>- U1
>[10/Oct/2000:14:45:16 -0700] conn=14 op=1 fd=32 closed
>error -5961 (TCP connection reset by peer.) - B4
>
>Client debug output:
>** Outstanding Requests:
> * msgid 2,  origid 2, status InProgress
>   outstanding referrals 0, parent count 0
>** Response Queue:
>   Empty
>do_ldap_select
>read1msg
>ber_get_next
>sockbuf_read: want=1, got=1
>  0000:  30                                           
>     0                 
>sockbuf_read: want=1, got=1
>  0000:  83                                           
>     .                 
>sockbuf_read: want=3, got=3
>  0000:  0e 40 ac                                     
>     .@.               
>ber_get_next failed.
>ldap_perror
>ldap_result: Can't contact LDAP server
>ldap_unbind
>ldap_free_request (origid 2, msgid 2)
>ldap_free_connection
>ldap_send_unbind
>ber_flush: 7 bytes to sd 3
>  0000:  30 05 02 01 03 42 00                         
>     0....B.           
>sockbuf_write: want=7, written=7
>  0000:  30 05 02 01 03 42 00                         
>     0....B.           
>ldap_free_connection: actually freed
>
>
>--- "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
>> >LDAP_SIZELIMIT_EXCEEDED.
>> 
>> Check the server logs for details.
>> 
>> >This despite the fact that
>> >I've set LDAP_OPT_SIZELIMIT and LDAP_OPT_TIMELIMIT
>> to
>> >LDAP_NO_LIMIT using the ldap_set_option() call.
>> 
>> Server may enforce restrictions beyond those
>> requested
>> by the client.  However, the result code
>> LDAP_SIZELIMIT_EXCEEDED
>> 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!?
>Get Yahoo! Mail - Free email you can access from anywhere!
>http://mail.yahoo.com/