Bug 138973

Summary: Openldap server can't create database with ldbm format
Product: Red Hat Enterprise Linux 3 Reporter: Rainer Traut <rainer.traut>
Component: openldapAssignee: Jan Safranek <jsafrane>
Status: CLOSED WONTFIX QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: nicole.haehnel, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:14:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
openldap server config none

Description Rainer Traut 2004-11-12 09:16:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; i-

Description of problem:
I'm trying to setup a ldap database for samba.
In my slapd.conf I have "database ldbm" like default.
But when starting the ldap server nothing happends. The 
directory /var/lib/ldap is empty.
I get an error with "slapcat -d 255":

slapcat startup: initiated.
backend_startup: starting database
=> ldbm_cache_open( "id2entry.dbb", 16, 600 )
<= ldbm_cache_open NULL "id2entry.dbb" errno=2 reason="No such file 
or directory")
Could not open/create id2entry.dbb
slapcat: could not open database.

I can't create a ldap database.

On Fedora Core 3 my config is working with database backend bdb, but 
not with ldbm.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. installing openldap-servers
2. editing /et/openldap/slapd.conf
3. starting ldap server
4. nothing happens
5. slapcat -d 255
6. error message: ldbm_cache_open NULL "id2entry.dbb" errno=2 
reason="No such file or directory")    

Additional info:

Comment 1 Rainer Traut 2004-11-12 09:18:10 UTC
Created attachment 106557 [details]
openldap server config

openldap server config file

Comment 2 RHEL Product and Program Management 2007-10-19 19:14:17 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.