LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 12-28-2011, 02:27 PM   #16
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by bathory View Post
make test can take a good amount of time to complete, so I tend to skip this step

If you want to rebuild a program compiled from sources, it's always better to run "make distclean" and if that's not available to run "make clean". And you should do this for both BerkeleyDB and openldap.
BTW since you're doing all this, I suggest you to use the latest openldap-2.4.28
Ok thanks again. I will get on it tomorrow with the newer version and see what we get.
For now, I think since I did a nice clean and rebuild of the database, without any errors, I'll leave that alone and concentrate on openldap tomorrow.

Thanks again Bathory !

Floyd
 
Old 12-29-2011, 07:32 AM   #17
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
make test can take a good amount of time to complete, so I tend to skip this step

If you want to rebuild a program compiled from sources, it's always better to run "make distclean" and if that's not available to run "make clean". And you should do this for both BerkeleyDB and openldap.
BTW since you're doing all this, I suggest you to use the latest openldap-2.4.28
I installed version 2.8. I ran all the tests. They looked good as far as I can see scrolling across the screen. ( there was no leftover log to look at )
So I tried again to start ldap with the command below. You can see the output. It looks like it starts but then just kills itself.
I don't find any logs that I can look at to see what's going on. Shouldn't there be a slapd log somewhere ? I saw nowhere to configure for one in the slapd.conf file.

One more thing I thought of.
I am not so sure about this part of the slapd.conf file.

# Load dynamic backend modules:
# modulepath %MODULEDIR%
moduleload back_bdb.la
# moduleload back_hdb.la
# moduleload back_ldap.la


For one thing, what is %MODULEDIR% supposed to point to, the berkly db libraries or what ?
For another, moduleload, we have nothing anywahere called back_bdb.la. What should that be pointing to. Maybe this is why things wont't start right ??


Please advise )

Thanks !!
Floyd


Ok, I figured out how to get more debugging. This is the most I can get ( -1 level ).
It seems to show that there is something it doesn't like in the core.schema. I got that from our other older ldap installation because I didn't see one in my new installation.
Is there somewhere I am supposed to get the core schema from ??


4efc6460 line 128 (attributetype ( 2.5.4.13 NAME 'description' DESC 'RFC2256: descriptive information' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ))
4efc6460 /usr/openldap-2.4.28/schemas/core.schema: line 128 attributetype: Duplicate attributeType: "2.5.4.13"
4efc6460 slapd.conf: line 6: <include> handler exited with 1!
4efc6460 slapd destroy: freeing system resources.
4efc6460 slapd stopped.
4efc6460 connections_destroy: nothing to destroy.


[root@prod-meteor1v4 slapd]# ./slapd -f slapd.conf -F /usr/openldap-2.4.28/servers/slapd -d 1
4efc5d03 @(#) $OpenLDAP: slapd 2.4.28 (Dec 28 2011 14:32:20) $
floydw@prod-meteor1v4.nslc.org:/usr/openldap-2.4.28/servers/slapd
ldap_pvt_gethostbyname_a: host=prod-meteor1v4.nslc.org, r=0
4efc5d03 daemon_init: listen on ldap:///
4efc5d03 daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap:///)
4efc5d03 daemon: listener initialized ldap:///
4efc5d03 daemon_init: 2 listeners opened
ldap_create
4efc5d03 slapd init: initiated server.
4efc5d03 slap_sasl_init: initialized!
4efc5d03 bdb_back_initialize: initialize BDB backend
4efc5d03 bdb_back_initialize: Berkeley DB 4.7.25: (May 15, 2008)
4efc5d03 hdb_back_initialize: initialize HDB backend
4efc5d03 hdb_back_initialize: Berkeley DB 4.7.25: (May 15, 2008)
4efc5d03 mdb_back_initialize: initialize MDB backend
4efc5d03 mdb_back_initialize: MDB 0.9.0: ("September 1, 2011")
4efc5d03 backend_startup_one: starting "cn=config"
4efc5d03 slapd destroy: freeing system resources.
4efc5d03 slapd stopped.
4efc5d03 connections_destroy: nothing to destroy.

Last edited by fwellers; 12-29-2011 at 08:03 AM.
 
Old 12-29-2011, 08:09 AM   #18
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 11,563

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Hi,

Quote:
[root@prod-meteor1v4 slapd]# ./slapd -f slapd.conf -F /usr/openldap-2.4.28/servers/slapd -d 1
You don't need the -F option. Try the same command without the "-F /usr/openldap-2.4.28/servers/slapd"
Regarding logs, take a look at /var/log/debug (at least this is where slapd write its logs on my Slackware)

Quote:
For one thing, what is %MODULEDIR% supposed to point to, the berkly db libraries or what ?
For another, moduleload, we have nothing anywahere called back_bdb.la. What should that be pointing to. Maybe this is why things wont't start right ??
If you didn't use "--enable-modules" while configuring the sources, you don't need any moduleload options.
 
Old 12-29-2011, 08:25 AM   #19
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
Hi,


You don't need the -F option. Try the same command without the "-F /usr/openldap-2.4.28/servers/slapd"
Regarding logs, take a look at /var/log/debug (at least this is where slapd write its logs on my Slackware)


If you didn't use "--enable-modules" while configuring the sources, you don't need any moduleload options.
Hi Bathory,
Well I may not have something set in my environment but I apparently need the -F dir option. If I try and run it without it, then nothing happens. I just get my prompt back.
Also, there is nothing in /var/log messages about this. I may have to look at syslog.conf and see where the default LOCAL4 logs to.

As far as modules, we'll need the backend database, that is where our ldap registry will be stored. So don't we have to load it ?

Thanks,
floyd
 
Old 12-29-2011, 09:07 AM   #20
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 11,563

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
The -F option is used when you're not using slapd.conf, but the cn=config DIT in order to configure your server. Using both of them makes slapd to try to convert slapd.conf into the necessary ldifs used by cn=config and write them into the directory specified by the -F option. See the slapd manpage for a better explanation

Regarding the modules, if you haven't used the "--enable-modules" option in ./configure, they are built statically into slapd, so you don't need that directive.

Could you post the slapd.conf you;re using to do your tests?
 
Old 12-29-2011, 09:16 AM   #21
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
The -F option is used when you're not using slapd.conf, but the cn=config DIT in order to configure your server. Using both of them makes slapd to try to convert slapd.conf into the necessary ldifs used by cn=config and write them into the directory specified by the -F option. See the slapd manpage for a better explanation

Regarding the modules, if you haven't used the "--enable-modules" option in ./configure, they are built statically into slapd, so you don't need that directive.

Could you post the slapd.conf you;re using to do your tests?
Thank you.
Can't say I really understand your first line. I appreciate you trying with me. I must have a mental block about understanding this, that I haven't gotten through yet.
btw, I got the logs going by editing syslog.conf to send local4.debug to a file.
Below is the slapd.conf I'm trying to get running.



#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#
#include %SYSCONFDIR%/schema/core.schema
include /usr/openldap-2.4.28/schemas/core.schema
include /usr/openldap-2.4.28/schemas/nchelp.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.
#referral ldap://root.openldap.org

#pidfile %LOCALSTATEDIR%/run/slapd.pid
#argsfile %LOCALSTATEDIR%/run/slapd.args
pidfile /usr/openldap-2.4.28/servers/run/slapd.pid
pidfile /usr/openldap-2.4.28/servers/run/slapd.args

# Load dynamic backend modules:
# modulepath %MODULEDIR%
moduleload back_bdb.la
# moduleload back_hdb.la
# moduleload back_ldap.la

# Sample security restrictions
# Require integrity protection (prevent hijacking)
# Require 112-bit (3DES or better) encryption for updates
# Require 63-bit encryption for simple bind
# security ssf=1 update_ssf=112 simple_bind=64

# Sample access control policy:
# Root DSE: allow anyone to read it
# Subschema (sub)entry DSE: allow anyone to read it
# Other DSEs:
# Allow self write access
# Allow authenticated users read access
# Allow anonymous users to authenticate
# Directives needed to implement policy:
# access to dn.base="" by * read
# access to dn.base="cn=Subschema" by * read
# access to *
# by self write
# by users read
# by anonymous auth
#
# if no access controls are present, the default policy
# allows anyone and everyone to read anything but restricts
# updates to rootdn. (e.g., "access to * by * read")
#
# rootdn can always read and write EVERYTHING!

#######################################################################
# BDB database definitions
#######################################################################

database bdb
suffix "o=meteorregistry.com"
rootdn "cn=nslcadmin,o=meteorregistry.com"
# 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 %LOCALSTATEDIR%/openldap-data
directory /usr/openldap-2.4.23/servers/openldap-data
# Indices to maintain
index objectClass eq
 
Old 12-29-2011, 09:44 AM   #22
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 11,563

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Please comment out the following 2 lines and try again
Quote:
pidfile /usr/openldap-2.4.28/servers/run/slapd.args
moduleload back_bdb.la
Also make sure that the schema files are in the correct location.

I'm again telling you to run "make install", so everything is installed in its correct place and run slapd from /usr/local/libexec/slapd (if you used no prefix in ./configure)
 
Old 12-29-2011, 10:05 AM   #23
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
Please comment out the following 2 lines and try again
Also make sure that the schema files are in the correct location.

I'm again telling you to run "make install", so everything is installed in its correct place and run slapd from /usr/local/libexec/slapd (if you used no prefix in ./configure)
Thank you.
I've done everything you said just now.
Here's the command I ran to get it started:
/usr/local/libexec/slapd -f /usr/openldap-2.4.28/servers/slapd/slapd.conf -d -1 >slapd.out 2>&1


And here is the output of slapd.out

4efc814e @(#) $OpenLDAP: slapd 2.4.28 (Dec 28 2011 14:32:20) $
floydw@prod-meteor1v4.nslc.org:/usr/openldap-2.4.28/servers/slapd
ldap_pvt_gethostbyname_a: host=prod-meteor1v4.nslc.org, r=0
4efc814e daemon_init: <null>
4efc814e daemon_init: listen on ldap:///
4efc814e daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap:///)
4efc814e daemon: listener initialized ldap:///
4efc814e daemon_init: 2 listeners opened
ldap_create
4efc814e slapd init: initiated server.
4efc814e slap_sasl_init: initialized!
4efc814e bdb_back_initialize: initialize BDB backend
4efc814e bdb_back_initialize: Berkeley DB 4.7.25: (May 15, 2008)
4efc814e hdb_back_initialize: initialize HDB backend
4efc814e hdb_back_initialize: Berkeley DB 4.7.25: (May 15, 2008)
4efc814e mdb_back_initialize: initialize MDB backend
4efc814e mdb_back_initialize: MDB 0.9.0: ("September 1, 2011")
4efc814e reading config file /usr/openldap-2.4.28/servers/slapd/slapd.conf
4efc814e line 6 (include /usr/openldap-2.4.28/schemas/core.schema)
4efc814e reading config file /usr/openldap-2.4.28/schemas/core.schema
4efc814e line 77 (attributetype ( 2.5.4.2 NAME 'knowledgeInformation' DESC 'RFC2256: knowledge information' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ))
4efc814e line 86 (attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' ) DESC 'RFC2256: last (family) name(s) for which the entity is known by' SUP name ))
4efc814e line 92 (attributetype ( 2.5.4.5 NAME 'serialNumber' DESC 'RFC2256: serial number of the entity' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} ))
4efc814e line 96 (attributetype ( 2.5.4.6 NAME ( 'c' 'countryName' ) DESC 'RFC2256: ISO-3166 country 2-letter code' SUP name SINGLE-VALUE ))
4efc814e line 100 (attributetype ( 2.5.4.7 NAME ( 'l' 'localityName' ) DESC 'RFC2256: locality which this object resides in' SUP name ))
4efc814e line 104 (attributetype ( 2.5.4.8 NAME ( 'st' 'stateOrProvinceName' ) DESC 'RFC2256: state or province which this object resides in' SUP name ))
4efc814e line 110 (attributetype ( 2.5.4.9 NAME ( 'street' 'streetAddress' ) DESC 'RFC2256: street address of this object' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ))
4efc814e line 114 (attributetype ( 2.5.4.10 NAME ( 'o' 'organizationName' ) DESC 'RFC2256: organization this object belongs to' SUP name ))
4efc814e line 118 (attributetype ( 2.5.4.11 NAME ( 'ou' 'organizationalUnitName' ) DESC 'RFC2256: organizational unit this object belongs to' SUP name ))
4efc814e line 122 (attributetype ( 2.5.4.12 NAME 'title' DESC 'RFC2256: title associated with the entity' SUP name ))
4efc814e line 128 (attributetype ( 2.5.4.13 NAME 'description' DESC 'RFC2256: descriptive information' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ))
4efc814e /usr/openldap-2.4.28/schemas/core.schema: line 128 attributetype: Duplicate attributeType: "2.5.4.13"
4efc814e /usr/openldap-2.4.28/servers/slapd/slapd.conf: line 6: <include> handler exited with 1!
4efc814e slapd destroy: freeing system resources.
4efc814e slapd stopped.
4efc814e connections_destroy: nothing to destroy.
 
Old 12-29-2011, 10:25 AM   #24
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 11,563

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Quote:
4efc814e line 128 (attributetype ( 2.5.4.13 NAME 'description' DESC 'RFC2256: descriptive information' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ))
4efc814e /usr/openldap-2.4.28/schemas/core.schema: line 128 attributetype: Duplicate attributeType: "2.5.4.13"
4efc814e /usr/openldap-2.4.28/servers/slapd/slapd.conf: line 6: <include> handler exited with 1!
Well I don't know why it's trying to read attributetype ( 2.5.4.13). In the core.schema that comes with openldap-2.4.28 it's commented out
 
Old 12-29-2011, 10:35 AM   #25
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
Well I don't know why it's trying to read attributetype ( 2.5.4.13). In the core.schema that comes with openldap-2.4.28 it's commented out
Remember I told you I couldn't find the core.schema, so I copied the one over from a previous version of our symas ldap.
Do you know where core.schema is ? I'll copy it into the schemas directory that I made.
 
Old 12-29-2011, 10:36 AM   #26
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by fwellers View Post
Remember I told you I couldn't find the core.schema, so I copied the one over from a previous version of our symas ldap.
Do you know where core.schema is ? I'll copy it into the schemas directory that I made.
never mind, I found it. I'll copy it over and try again.
 
Old 12-29-2011, 11:00 AM   #27
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by fwellers View Post
Remember I told you I couldn't find the core.schema, so I copied the one over from a previous version of our symas ldap.
Do you know where core.schema is ? I'll copy it into the schemas directory that I made.
Oh yea !
root 20154 18054 0 10:56 pts/1 00:00:00 /usr/local/libexec/slapd -f /usr/openldap-2.4.28/servers/slapd/slapd.conf -d -1

So I moved the DB_CONFIG file where it was supposed to go, put the proper schema.core file in place and now I have slapd running in the foreground.
Above is the actual process.
Things look good so far.

Next I have to try and configure it somehow so it can talk to my ldap browser and I can see, modify ldif files through it.

Any ideas what is next ?

So many thanks for helping me get this far !!
 
Old 12-29-2011, 11:38 AM   #28
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
Well I don't know why it's trying to read attributetype ( 2.5.4.13). In the core.schema that comes with openldap-2.4.28 it's commented out
Another problem sprang up.
I am not sure if there is a start / stop script to modify that does proper shutdowns and startups.
When I started it before I just did it in the foreground with:
/usr/local/libexec/slapd -f /usr/openldap-2.4.28/servers/slapd/slapd.conf -d 1

I eventually control c'd that. I tried to start it again and apparently since I didn't shut it down correctly the database is corrupted and it wont' start now.
Can you point me right here ?

Thank you,
Floyd



member $ owner $ roleOccupant $ PreferredTransport $ PreferredEncryption $ Contact ) )
4efc96e0 2.5.13.0 (objectIdentifierMatch): 4efc96e0 matchingRuleUse: ( 2.5.13.0 NAME 'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $ supportedFeatures $ supportedApplicationContext ) )
4efc96e0 slapd startup: initiated.
4efc96e0 backend_startup_one: starting "cn=config"
4efc96e0 config_back_db_open
4efc96e0 config_build_entry: "cn=config"
4efc96e0 config_build_entry: "cn=schema"
4efc96e0 >>> dnNormalize: <cn={0}core>
4efc96e0 <<< dnNormalize: <cn={0}core>
4efc96e0 config_build_entry: "cn={0}core"
4efc96e0 >>> dnNormalize: <cn={1}nchelp>
4efc96e0 <<< dnNormalize: <cn={1}nchelp>
4efc96e0 config_build_entry: "cn={1}nchelp"
4efc96e0 config_build_entry: "olcDatabase={-1}frontend"
4efc96e0 config_build_entry: "olcDatabase={0}config"
4efc96e0 config_build_entry: "olcDatabase={1}bdb"
4efc96e0 backend_startup_one: starting "o=meteorregistry.com"
4efc96e0 bdb_db_open: database "o=meteorregistry.com": unclean shutdown detected; attempting recovery.
4efc96e0 bdb_db_open: database "o=meteorregistry.com": dbenv_open(/usr/openldap-2.4.28/servers/slapd/openldap-data).
4efc96e0 bdb(o=meteorregistry.com): /usr/openldap-2.4.28/servers/slapd/openldap-data/logs: No such file or directory
4efc96e0 bdb(o=meteorregistry.com): PANIC: No such file or directory
4efc96e0 bdb(o=meteorregistry.com): unable to join the environment
4efc96e0 bdb_db_open: database "o=meteorregistry.com" cannot be recovered, err -30974. Restore from backup!
4efc96e0 ====> bdb_cache_release_all
4efc96e0 bdb(o=meteorregistry.com): txn_checkpoint interface requires an environment configured for the transaction subsystem
4efc96e0 bdb_db_close: database "o=meteorregistry.com": txn_checkpoint failed: Invalid argument (22).
4efc96e0 backend_startup_one (type=bdb, suffix="o=meteorregistry.com"): bi_db_open failed! (-30974)
4efc96e0 slapd shutdown: initiated
4efc96e0 ====> bdb_cache_release_all
4efc96e0 bdb_db_close: database "o=meteorregistry.com": alock_close failed
4efc96e0 slapd destroy: freeing system resources.
4efc96e0 slapd stopped
 
Old 12-29-2011, 12:14 PM   #29
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 11,563

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
I'm using the attached script to start/stop openldap and never had such problems. If you want to use it change LD_LIBRARY_PATH accordingly.

Quote:
4efc96e0 bdb(o=meteorregistry.com): /usr/openldap-2.4.28/servers/slapd/openldap-data/logs: No such file or directory
Check DB_CONFIG to see why it's trying to write the logs in that directory, By defaults logs are written to the same directory where DB_CONFIG is located (it should be the directory defined by the "directory" directive in slapd.conf)
Attached Files
File Type: txt rc.openldap.txt (1.2 KB, 9 views)
 
Old 12-29-2011, 12:23 PM   #30
fwellers
Member
 
Registered: Dec 2011
Posts: 32

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bathory View Post
I'm using the attached script to start/stop openldap and never had such problems. If you want to use it change LD_LIBRARY_PATH accordingly.

Check DB_CONFIG to see why it's trying to write the logs in that directory, By defaults logs are written to the same directory where DB_CONFIG is located (it should be the directory defined by the "directory" directive in slapd.conf)
Thanks.
I will check out and use your script. I appreciate it.
As for the start problem.
I told it in the slapd.conf that the data files go into that directory. Then it told me I need to put DB_CONFIG in there. that seemed fine. It started up the first time.
Then after I stopped it it wouldn't start again.
During troubleshooting that, I figured I'd start it from scratch so I removed all the database stuff from that directory.
that caused the log error. Apparently it needs to be able to write to logs.
So I created the log directory in there and it gets further now. It makes a bunch of databases in there as evidenced by this ls :

[root@prod-meteor1v4 slapd]# ls openldap-data
alock __db.001 __db.002 __db.003 __db.004 __db.005 __db.006 DB_CONFIG logs

But it fails trying to create a database called id2entry.bdb ( see below )


4efca081 slapd startup: initiated.
4efca081 backend_startup_one: starting "cn=config"
4efca081 config_back_db_open
4efca081 config_build_entry: "cn=config"
4efca081 config_build_entry: "cn=schema"
4efca081 >>> dnNormalize: <cn={0}core>
4efca081 <<< dnNormalize: <cn={0}core>
4efca081 config_build_entry: "cn={0}core"
4efca081 >>> dnNormalize: <cn={1}nchelp>
4efca081 <<< dnNormalize: <cn={1}nchelp>
4efca081 config_build_entry: "cn={1}nchelp"
4efca081 config_build_entry: "olcDatabase={-1}frontend"
4efca081 config_build_entry: "olcDatabase={0}config"
4efca081 config_build_entry: "olcDatabase={1}bdb"
4efca081 backend_startup_one: starting "o=meteorregistry.com"
4efca081 bdb_db_open: database "o=meteorregistry.com": dbenv_open(/usr/openldap-2.4.28/servers/slapd/openldap-data).
4efca081 bdb_db_open: database "o=meteorregistry.com": db_open(/usr/openldap-2.4.28/servers/slapd/openldap-data/id2entry.bdb) failed: No such file or directory (2).
4efca081 ====> bdb_cache_release_all
4efca081 backend_startup_one (type=bdb, suffix="o=meteorregistry.com"): bi_db_open failed! (2)
4efca081 slapd shutdown: initiated
4efca081 ====> bdb_cache_release_all
4efca081 bdb_db_close: database "o=meteorregistry.com": alock_close failed
4efca081 slapd destroy: freeing system resources.
4efca081 slapd stopped.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenLDAP complains of Berkeley DB version mismatch [GOD]Anck Slackware 7 06-08-2009 02:54 AM
Version incompatible (OpenLDAP) Hawkin Linux - Software 16 06-20-2008 05:08 AM
OpenLDAP with ssl version compatability Vikas Sarin Linux - Networking 0 12-17-2006 09:46 PM
Openldap BerkeleyDB version imcompatible kgao Linux - Software 3 04-12-2005 08:26 PM
Segmentation fault after OpenLDAP / Berkley DB (Slackware 8.1) cereal Linux - General 0 07-17-2003 01:34 PM


All times are GMT -5. The time now is 11:40 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration