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

Re: Problem chasing multiple referrals (ITS#799)



This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=_80D86E57.BEDFBDF9
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Could you send me the complete trace?
-Steve


>>> <venaas@uninett.no> 03-Oct-00 8:03:37 AM >>>
Full_Name: Stig Venaas
Version: 2.0.4
OS: Linux
URL:=20
Submission from: (NULL) (158.38.60.92)


If I do

ldapsearch -h sipus.uninett.no -b "dc=3Dhisf,dc=3Dno" "cn=3DStig*"

I get two referrals, when following those and turning on debugging

ldapsearch -C -d65535 -h sipus.uninett.no -b "dc=3Dhisf,dc=3Dno" "cn=3DStig=
*"

ldapsearch will hang, ending with:

** Outstanding Requests:
* msgid 5,  origid 2, status Request Completed
   outstanding referrals 0, parent count 1
* msgid 2,  origid 2, status Request Completed
   outstanding referrals 1, parent count 0
** Response Queue:
* msgid 2,  type 100
   chained responses:
  * msgid 2,  type 100
  * msgid 2,  type 100
  * msgid 2,  type 100
  * msgid 2,  type 100
  * msgid 2,  type 100
* msgid 4,  type 97
do_ldap_select

It looks like it got all the data it should, it just hasn't realised it. =
The
LDAP servers are publicly available so you can hopefully reproduce this. I =
can
try to debug more myself but some pointers would be nice, the code isn't
trivial.

Stig

--=_80D86E57.BEDFBDF9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 8pt MS Sans Serif; MARGIN-LEFT: =
2px">
<DIV><FONT size=3D1>Could you send me the complete trace?</FONT></DIV>
<DIV><FONT size=3D1>-Steve</FONT></DIV>
<DIV><BR><BR>&gt;&gt;&gt; &lt;venaas@uninett.no&gt; 03-Oct-00 8:03:37 =
AM=20
&gt;&gt;&gt;<BR>Full_Name: Stig Venaas<BR>Version: 2.0.4<BR>OS: Linux<BR>UR=
L:=20
<BR>Submission from: (NULL) (158.38.60.92)<BR><BR><BR>If I do<BR><BR>ldapse=
arch=20
-h sipus.uninett.no -b "dc=3Dhisf,dc=3Dno" "cn=3DStig*"<BR><BR>I get two =
referrals,=20
when following those and turning on debugging<BR><BR>ldapsearch -C -d65535 =
-h=20
sipus.uninett.no -b "dc=3Dhisf,dc=3Dno" "cn=3DStig*"<BR><BR>ldapsearch =
will hang,=20
ending with:<BR><BR>** Outstanding Requests:<BR>* msgid 5,&nbsp; origid =
2,=20
status Request Completed<BR>&nbsp;&nbsp; outstanding referrals 0, parent =
count=20
1<BR>* msgid 2,&nbsp; origid 2, status Request Completed<BR>&nbsp;&nbsp;=20=

outstanding referrals 1, parent count 0<BR>** Response Queue:<BR>* =
msgid=20
2,&nbsp; type 100<BR>&nbsp;&nbsp; chained responses:<BR>&nbsp; * msgid =
2,&nbsp;=20
type 100<BR>&nbsp; * msgid 2,&nbsp; type 100<BR>&nbsp; * msgid 2,&nbsp; =
type=20
100<BR>&nbsp; * msgid 2,&nbsp; type 100<BR>&nbsp; * msgid 2,&nbsp; type =
100<BR>*=20
msgid 4,&nbsp; type 97<BR>do_ldap_select<BR><BR>It looks like it got all =
the=20
data it should, it just hasn't realised it. The<BR>LDAP servers are =
publicly=20
available so you can hopefully reproduce this. I can<BR>try to debug more =
myself=20
but some pointers would be nice, the code=20
isn't<BR>trivial.<BR><BR>Stig<BR></DIV></BODY></HTML>

--=_80D86E57.BEDFBDF9--