[Date Prev][Date Next]
RE: Simple Paged Results Extension
From: Pierangelo Masarati [mailto:email@example.com]
Sent: Wednesday, February 18, 2004 1:50 PM
Subject: RE: Simple Paged Results Extension
>> I still can't keep slapd from crashing every time I do an
>> ldapmodify/ldapadd. After it crashes, it won't restart again until
>> /var/lib/ldap is cleared out. This doesn't happen when I use ldbm.
>> slapd crashes with:
>> <= index_entry_add( 1, "dc=com" ) success
> this is anything but a valid DN; can you provide
> an excerpt of the .ldif that is causing the crash?
> The crash itself might (and is likely to be) a
> bug, but your input sounds incorrect. It is
> captured by an assertion, that's why the server
> "crashes"; actually, it's dying with a precise
> indication of the reason of failure.
>> => bdb_dn2id( "" )
>> <= bdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found
>> => bdb_dn2id_add( "cn=ldapsync,", 0x00000002 )
>> slapd: dn.c:696: dnParent: Assertion `( ( ( ( (p[ 0 ]) >= 'a' && (p[ 0
>> ]) <= 'z' ) || ( (p[ 0 ]) >= 'A' && (p[ 0 ]) <= 'Z' ) ) ) || ( ( (p[ 0
>> ]) >= '0' && (p[ 0 ]) <= '9' ) ) )' failed.
>> ldapmodify crashes with:
>> Enter LDAP Password:
>> adding new entry "dc=com"
>> ldapadd: update failed: dc=com
>> ldap_add: Can't contact LDAP server (-1)
> The ldif I'm trying to import is simply:
> dn: dc=com
> objectClass: organization
> objectClass: dcObject
> o: com
> dc: com
> It has always worked fine (obviously, as a start) when using ldbm. Is
> there something wrong here? My base dn in slapd.conf is "", is that
> inappropriate? If so, how else can I create base objects without getting
> "parent does not exist" etc.?
The ldif is fine; with bdb I'm pretty sure it works
if you set the suffix to "dc=com"; I haven't been
playing with suffix "" for a while, so it might be
broken, AFAIK, but sure you don't need it for a
I suggest you file an ITS about this, anyway.
Is there something wrong with the way I'm compiling db 4.2.52 or openldap
2.2.5? I swear I've seen others who have been able to get this working. It's
also a little troubling that 'DB_NOTFOUND: No matching key/data pair found'
shows up no where, but perhaps this is a bdb-specific problem.