Home / server / Questions / 382893
Accepted
Infotechie
Asked: 2012-04-26 01:12:30 +0800 CST

How to know which berkley db openldap is refering to?

  • 772

I have two berkeley dbs installed on the RHEL 5.3. Now, I am confused that which one openldap is referring as its backend.

Following is the slapd.conf:

include /usr/local/etc/openldap2-4-30/schema/core.schema
include /usr/local/etc/openldap2-4-30/schema/cosine.schema
include /usr/local/etc/openldap2-4-30/schema/inetorgperson.schema

**# Define global ACLs to disable default read access.**

**# Do not enable referrals until AFTER you have a working directory**
**# service AND an understanding of referrals.**                  

pidfile /usr/local/var/openldap2-4-30/run/slapd.pid
argsfile    /usr/local/var/openldap2-4-30/run/slapd.args

**# rootdn can always read and write EVERYTHING!**
access to *
    by self write
    by * read

#########################################
**# uniquely identifies this server**
#########################################
serverID 1

#######################################################################
**# BDB database definitions**
#######################################################################
database bdb
suffix "dc=COMPANY,dc=CP"
rootdn "cn=Manager,dc=COMPANY,dc=CP"

**# Cleartext passwords, especially for the rootdn, should**
**# be avoid. See slappasswd(8) and slapd.conf(5) for details.**
**# Use of strong authentication encouraged.**
rootpw secret   

**# The database directory MUST exist prior to running slapd AND**
**# should only be accessible by the slapd and slap tools.**
**# Mode 700 recommended.**
directory   /usr/local/var/openldap2-4-30/Master1/openldap-data

Please guide how can i know that out of which installed berkeley dbs, openldap is using as its backend?

Note: this question is linked to

slapd not running

Thanking you.

redhat installation openldap configuration berkeleydb

4 Answers

  1. Best Answer

    It looks like you should only have 1 root there, each new root contains a 

    database        bdb
suffix  "dc=limepepper,dc=org"
directory       /var/lib/ldap/mycompany.org

    type block.

    Have you initialized the new root?

    I think you need to create a new root ldif file, and import those entries into the running LDAP server like so;

    # cat /home/myuser/mynewroot.ldif
dn: dc=COMPANY,dc=CP
objectclass: dcObject
objectclass: organization
o: COMPANY CP
dc: COMPANY

dn: cn=Manager,dc=COMPANY,dc=CP
objectclass: organizationalRole
cn: Manager

    and then import that into the empty LDAP server like so;

    # ldapadd -x -D "cn=Manager,dc=COMPANY,dc=CP" -W -f   /home/myuser/mynewroot.ldif

    There is a tutorial on setting up new roots here;
    http://www.howtoforge.com/linux_openldap_setup_server_client

    and some more details on what you need in the minimal root here;
    http://www.openldap.org/doc/admin22/dbtools.html

    • 1

  2. The database OpenLDAP is using is located at /usr/local/var/openldap2-4-30/Master1/openldap-data.

    • 0

  3. How about:

    $ ldd <path-to-slapd> | grep libdb

    ?

    • 0

  4. It seems you have been mixing several sources (both information and software....) while you've been wrestling with OpenLDAP. My recommendation: start over from scratch.

    For starters, if you yum install openldap-servers, you absolutely DO NOT need to download any BDB libraries from the net, everything is set for you.

    Secondly, the "standard" path for OpenLDAP data files is /var/lib/ldap. Normally you should not care about that, you create LDIF files with the text editor of your choice and then use slapadd command to create those LDAP trees. After that, use standard LDAP utilities such as Luma, gq, ldapsearch/ldapadd/ldapremove or your favourite programming language LDAP bindings.

    Here's an excellent on-line book about (Open)LDAP, don't get scared by the title.

    • 0