[Date Prev][Date Next]
Re: Openldap referral chasing issue
- To: OpenLDAP-bugs@OpenLDAP.org
- Subject: Re: Openldap referral chasing issue
- From: Chi-Cheng Lee <email@example.com>
- Date: Tue, 7 Feb 2006 15:10:41 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fed1njTSAxVdMFyoZltL8W+WHdrVo1AHOfMaAGXLTfOAO4YIy2ZL0EQQfC8Hz9PZFcoBapmMW7K2WyGttXuObureX4ujlKL+rIYW2VTl5NHArdhXkZKYnWbqe/D9tTLOobclui5oxHgUAheSSkuCO1C/ZeKWZALssDi/7xOLFkg=
I also experienced the same problem. In my case, I have AD back-end and access through LDAP.
There are one root domain and three sub domains. I did a sub tree search from the root domain with filter "(samAccountName=eric)" and all attributes.
There are 10 referrals being chased and then suddenly the SEGV. The ldap debug log snippet follows:
2006-02-07 03:01:03: wait4msg continue, msgid 22, all 1
2006-02-07 03:01:03: ldap_chkResponseList for msgid=22, all=1
2006-02-07 03:01:03: ldap_chkResponseList returns NULL
2006-02-07 03:01:03: ldap_int_select
2006-02-07 03:01:06: read1msg: msgid 22, all 1
2006-02-07 03:01:06: ldap_read: message type bind msgid 22, original id 22
2006-02-07 03:01:06: new result: res_errno: 0, res_error: <>, res_matched: <>
2006-02-07 03:01:06: read1msg: 0 new referrals
2006-02-07 03:01:06: read1msg: mark request completed, id = 22
2006-02-07 03:01:06: request 22 done
2006-02-07 03:01:06: res_errno: 0, res_error: <>, res_matched: <>
2006-02-07 03:01:06: ldap_free_request (origid 22, msgid 22)
2006-02-07 03:01:06: ldap_free_connection
2006-02-07 03:01:06: ldap_free_connection: refcnt 1
2006-02-07 03:01:06: ldap_parse_result
2006-02-07 03:01:06: ldap_msgfree
2006-02-07 03:01:06: read1msg: 1 new referrals
I would appreciate any insight on this issue.
On Wed, 2006-02-01 at 00:26 +0530, Kala B wrote:
> Is this a known issue ? I am using the latest openldap version.
> Any thoughts which helps me remove the crash would be of great help.
This by no means qualifies as a bug report. Please follow instructions
reported here <http://www.openldap.org/faq/data/cache/56.html
produce something that may allow developers to track, reproduce and fix
the issue, if any. Unless you can come up with an evidence of a bug in
OpenLDAP software (just "it crashes" is not by itself evidence of a
bug), please direct further discussion to the OpenLDAP-software mailing