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

Re: Uninvited listener?



Am Sonntag 23 November 2008 20:57:46 schrieb Howard Chu:
> Most likely you are both seeing a bug in glibc, documented in our ITS#5251.
To workaround the problem remove "localhost", from the "::1" line in 
/etc/hosts. The underlying glibc problem will be fixed with openSUSE 11.1.

regards,
	Ralf

> Chris Evans wrote:
> > I am new to LDAP, and am trying to get OpenLDAP installed on a computer
> > running SUSE 11.0.  (Actually, I did this on two similarly configured
> > machines with the same result.)  Everything goes smoothly up until the
> >
> > "make test" step, which produces:
> >      >>>>>  Starting test000-rootdse ...
> >
> >      running defines.sh
> >      Starting slapd on TCP/IP port 9011...
> >      Using ldapsearch to retrieve the root DSE...
> >      Waiting 5 seconds for slapd to start...
> >         [omitting repeats]
> >      ./scripts/test000-rootdse: line 66: kill: (4683) - No such process
> >      ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
> >
> >      >>>>>  Test failed
> >      >>>>>  ./scripts/test000-rootdse failed (exit 255)
> >
> >      make[2]: *** [bdb-yes] Error 255
> >      make[2]: Leaving directory
> > `/usr/local/pkg/openldap/openldap-2.4.11/tests' make[1]: *** [test] Error
> > 2
> >      make[1]: Leaving directory
> > `/usr/local/pkg/openldap/openldap-2.4.11/tests' make: *** [test] Error 2
> >
> > The file slapd1.l.log in tests/testrun ends with the following:
> >      >>>  dnNormalize:<cn=Write>
> >
> >      <<<  dnNormalize:<cn=write>
> >      slapd starting
> >      daemon: listen(ldap://localhost:9011/, 5) failed errno=98 (Address
> > already in use) slapd shutdown: initiated
> >      ====>  bdb_cache_release_all
> >      slapd destroy: freeing system resources.
> >      slapd stopped.
> >
> > I found another thread on this list that suggested slapd might already be
> > running, but in my case a check of processes found nothing including
> > "slapd" or "ldap".  I also found threads suggesting that this kind of
> > error can be caused by IPv6, so I repeated everything with the option
> > --enable-ipv6=no with the same result.  I also tried adding the line ALL:
> > ALL : ALLOW in hosts.allow, which didn't help either.
> >
> > Suggestions?  Thanks.