Re: error that doesn't make sense to me

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Sunday, January 02, 2005 6:45 PM -0700 Craig White 
<craigwhite@azapple.com> wrote:

> On Sun, 2005-01-02 at 17:32 -0800, Kurt D. Zeilenga wrote:
> > At 04:36 PM 1/2/2005, Craig White wrote:
> > > Trying to connect to openldap server - the following snippet is logged
> > > which I think comprises my error
> > >
> > > Jan  2 17:24:29 linuxserver slapd[3620]: send_ldap_result: conn=1608
> > > op=2 p=3
> > > Jan  2 17:24:29 linuxserver slapd[3620]: send_ldap_result: err=0
> > > matched="" text=""
> > > Jan  2 17:24:29 linuxserver slapd[3620]: send_ldap_response: msgid=3
> > > tag=101 err=0
> >
> >  From the above, I deduce that the server is responding to an LDAPv3
> > search request, msgid=2, with result code of success (0).
> >
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_get(32)
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_get(32): got
> > > connid=1608
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_read(32): checking
> > > for input on id=1608
> > > Jan  2 17:24:29 linuxserver slapd[3620]: ber_get_next on fd 32 failed
> > > errno=0 (Success)
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_read(32): input
> > > error=-2 id=1608, closing.
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_closing: readying
> > > conn=1608 sd=32 for close
> > > Jan  2 17:24:29 linuxserver slapd[3620]: connection_close: conn=1608
> > > sd=32
> >
> > This indicates the TCP stream was closed.  I note the closure appears to
> > abrupt.  That is, the client does not appear to send a Unbind request
> > before disconnecting from the server.
> >
> > > Input error -2  Is that my error? How to interpret?
> >
> > This -2 indicates that ber_get_next failure requires the server to close
> > the TCP stream, which it then does.
> ----
> OK then - can you suggest a log level that I can use (I have set a lot
> of different combinations) that will help me diagnose where I am going
> wrong with client connection? I see the codes from man slapd.conf but
> each one I try doesn't help me see what isn't working.

You might try starting slapd with the -d -1 flag.  That will cause it not 
to fork, and send out a ton of debugging info.  I suggest catching 
stdout/stderr into a file when doing this so you can parse through it 
there, rather than having it stream by.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin