[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: dn2id could not open dn2id.dbb
The directory that I am storing all ldbm files in (as specified by the
directory pragma in slapd.conf) is /usr/local/ldbmdir, which exists and
contains the following files:
artdev:/usr/local/ldbmdir# ls -la
total 112
drwxr-xr-x 2 root system 512 Mar 29 15:30 ./
drwxr-xr-x 19 root system 512 Mar 27 15:07 ../
-rw-r--r-- 1 root system 3 Mar 29 16:59 NEXTID
-rw------- 1 root system 2048 Mar 29 15:30 dn.dbb
-rw------- 1 root system 2048 Mar 29 15:36 dn2id.dbb
-rw------- 1 root system 2048 Mar 29 15:36 id2children.dbb
-rw------- 1 root system 14336 Mar 29 16:59 id2entry.dbb
-rw------- 1 root system 2048 Mar 29 15:30 o.dbb
-rw------- 1 root system 2048 Mar 29 15:30 objectclass.dbb
-rw------- 1 root system 4096 Mar 29 15:30 rtn.dbb
-rw------- 1 root system 2048 Mar 29 15:30 uid.dbb
artdev:/usr/local/ldbmdir#
However, when I do an "ldbmcat" on the files, the ONLY one that contains
something other than blank lines is "id2entry.dbb", which is why, I'm
assuming,
slapd complains abotu the dn2id.dbb problem. Is this indicitave of some
other problem, perhaps with my naming scheme?
thanks again,
-Andrew
-----Original Message-----
From: Neil Hunter [mailto:neil.hunter@theplanet.net]
Sent: Thursday, March 30, 2000 12:59 AM
To: Andrew Kornuta
Cc: OpenLDAP-software
Subject: Re: dn2id could not open dn2id.dbb
On Wed, 29 Mar 2000, Andrew Kornuta wrote:
> Anyhow, when I attempt to do an ldapsearch -b "rtn=987654321, o=Digital
> Insight" "rtn=987654321" (rtn is an attribute that I added to a new object
> class. The object class is defined in slapd.oc.conf, and all the
attributes
> are in slapd.at.conf. It is a fully qualified Distinguished Name) the
> command returns "ldap_search: No such object" and on the console (where
> slapd is running in full debug mode) I see the message "<= dn2id could not
> open dn2id.dbb".
>
> Anyone have any ideas?
dn2id.dbb is the database file that maps DN's onto the internal ID of an
entry.
If this file cannot be found it suggests that there is a problem with the
underlying database.
If you run slapd with a "-d 1" and look for the ldbm_cache_open lines, you
should see the full path that the slapd is trying to open.
Check your "directory" line in your slapd.conf - it should point to the
filesystem location for the various database files. If this directory exists
and contains files, check the permissions and ownerships to make sure the
slapd
can read them.
If the directory doesn't exist or is empty you need to use ldif2ldbm to turn
your LDIF into the necessary database files.
Cheers,
Neil
----------------------------------------------------------------------------
---
Neil Hunter Tel: +44 (0)113 234
6073
Internet Systems Developer Fax: +44 (0)113 234
6065
Planet Online Limited Mobile: +44 (0)7787 100
649
----------------------------------------------------------------------------
---