Re: openldap unstable on Solaris 2.6 SPARC

[Roland Rosenfeld <rrosenfeld@netcologne.de>]

On Mon, 09 Apr 2001, Ward Vandewege wrote:

> I have a problem with an unstable openldap tree on a Solaris 2.6
> box.  Here's some information about the setup:
> 
> OpenLDAP 2.0.7

Is 2.0.7 really "unstable"?  I thought that this is the stable release
(in contrast to the CVS version)?  Should I downgrade to 1.2.11 to
avoid problems with 2.0.7?

> Solaris 2.6 with patches (I can provide a list if necessary)

I had one "no data for entry" on Solaris 2.7 with GDBM.
On Solaris 2.8 (using a binary compiled with Solaris 2.7 and a patched
libc from Sun) with db-3.2.9 I have five "no data for entry" in my
database.

Sometimes I notice, that some entry isn't found with a special key.
When I search with a different attribute as key, I find the entry.
slapindex didn't help until I noticed, that this seems to stop at the
first "no data for entry", so slapindex needs to be called with -c,
too.

> The effect is that the openldap server simply dies, with nothing
> special in the logs on loglevel 256. Sometimes it dies 2 times a
> day, sometimes it works fine for three days.

I never noticed something like this.

> Also, we have noticed that slapcat gives errors when trying to
> create an ldif file of the database. This is the typical output:
> 
> # /usr/local/sbin/slapcat -l /usr/local/etc/openldap/outputfile.ldif
> # no data for entry id=00000b9

Same here.
 
> I would greatly appreciate any ideas/comments/suggestions.

Sorry, I only can tell you that I have similar problems.

Tschoeeee

        Roland