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

Re: Search results not complete at base level after slapd start



Hall, Ken (IDS ECCS) wrote:

Yes, I tried that first thing.

I've copied the database to a test system, and the problem appears consistently on the first search after slapd starts.  The first search ALWAYS omits the last two DN's from the base.  Subsequent
searches return all entries, as follows:
Did you only copy the DB-Files or did you dump the the DB with slapcat
(and import the dump with slapadd into the test system)?
Sometimes, the slapindex can't repair the index, so it is necessary to

1. export the hole DB with slapcat
2. to delete all DB-files
3. to reimport the DB with slapadd.

Particularly, this is recommendable if you upgrade your slapd.

regards
Andreas





kehall@lnxken8:~/bin> ldapsearch -x cn=uidmin
# extended LDIF
#
# LDAPv3
# filter: cn=uidmin
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1
kehall@lnxken8:~/bin> ldapsearch -x cn=uidmin
# extended LDIF
#
# LDAPv3
# filter: cn=uidmin
# requesting: ALL
#

# uidmin, ml.com
dn: cn=uidmin,dc=ml,dc=com
objectClass: top
objectClass: applicationProcess
objectClass: extensibleObject
cn: uidmin
uidNumber: 67342

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1




-----Original Message-----
From: Andreas Gabriel [mailto:gabriel@hrz.uni-marburg.de]
Sent: Monday, November 17, 2003 11:08 AM
To: Hall, Ken (IDS ECCS)
Cc: openldap-software@OpenLDAP.org
Subject: Re: Search results not complete at base level after slapd start



Hi Ken,

have you rebuild your index (see >man slapindex)?
Probably, your DB-index is corrupt.

regards
andreas



Hall, Ken (IDS ECCS) wrote:


Running Openldap 2.1.4, the base of my directory tree

contains seven entries in the following order: Two admin accounts, "ou=People", "ou=Groups", "ou=mounts", "cn=uidmin", and "cn=uidmax".


The last two entries store the "next available UID number"

range for my maintenance scripts.

This worked fine with Openldap 2.0, but I've noticed since

upgrading to 2.1 that when slapd first starts, searches will not return all of the DN's at the base of the tree. The ones missing are always


happen to be the last two or three added, which happen to

be the "mounts", "uidmin" and "uidmax" entries. This is the case for both generic searches, and specific ones like "cn=uidmin".


The admin accounts, "people", and "groups" are always

found. "mounts" will be missing occasionally (causing automount problems), and "uidmin" and "uidmax" are almost always missing right after


starting slapd.

If I repeat the search a few times, it eventually finds the

entries, but this causes problems with my maintenance scripts. The behavior is present both for ldapsearch, and a Windows-based LDAP


browser, so I know it's not just the search process failing.

Since the problem is so intermittent, I'm not sure how to

go about writing a bug report for it. I'm going to try to duplicate it in a controlled environment.


I can't easily upgrade Openldap. The distro I'm using has

somewhat backleveled build utilities, so recent versions won't build. Upgrading the build utilities turned into a serious mess, so I've


given it up for now. If there's a fix for this problem, I

can get the distro vendor to implement it in 2.1.4 though.

Has anyone seen this?  Is there a solution?  Thanks.



--
-- Andreas Gabriel
@AG Neurophysik ,Renthof 7, 35032 Marburg TEL/FAX +49 +6421 28-25683/27034
@HRZ, Hans-Meerwein-Str. , 35032 Marburg TEL/FAX +49 +6421 28-23560/26994
------------------ Philipps-Universitaet Marburg -------------------------







--
--  Andreas Gabriel
@AG Neurophysik ,Renthof 7, 35032 Marburg TEL/FAX +49 +6421 28-25683/27034
@HRZ, Hans-Meerwein-Str.  , 35032 Marburg TEL/FAX +49 +6421 28-23560/26994
------------------ Philipps-Universitaet Marburg -------------------------