[Date Prev][Date Next]
RE: (ITS#4216) slapd terminates unexpectedly
I'll try to capture this error in a debugger as Howard suggested. I'm
surprised though that you were unable to reproduce it as yet. We've
been able to do it here on several different machines ranging from a
dual CPU Ultra-60 with 1GB of RAM up to a 24 core E2900 with 48GB of
RAM. Are you by any chance trying to reproduce this on a single CPU
(with a single core) machine?
From: Quanah Gibson-Mount [mailto:firstname.lastname@example.org]
Sent: Friday, December 02, 2005 1:37 PM
Cc: James MacNider
Subject: RE: (ITS#4216) slapd terminates unexpectedly
--On Friday, December 02, 2005 1:30 PM -0500 James MacNider
> Hello Quanah,
> As I mentioned earlier to Howard Chu, my slapd.conf simply contains
> backend null
> database null
> suffix ""
> rootdn "cn=root"
> bind on
># Cleartext passwords, especially for the rootdn, should # be avoid.
> See slappasswd(8) and slapd.conf(5) for details.
># Use of strong authentication encouraged.
> rootpw secret
> So I never set a syslog level in slapd.conf. What is that value by
>From the slapd.conf(5) man page:
if no loglevel (or a 0 level) is defined, no
logging occurs, so at least the none level is required
to have high priority messages logged.
> Also the only options I set during the whole configure/make/make test
> sequence of the code was for the configure where I set these flags:
> --enable-bdb=no --enable-null=yes --enable-hdb=no ...So from this
> syslog should not have been disabled at build time either.
Given the above, I think whether or not the support for it exists
doesn't really matter. ;)
> Thanks for continuing to follow up with this issue.
Certainly. Still no luck reproducing it however.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: