readthefuckingmanual.net

[SOLVED] bdb_db_open: Warning - No DB_CONFIG file found in directory /var/lib/openldap-data: (2) Expect poor performance for suffix

Error added: 2007-10-10T13:48:27Z

2 people waiting for the answer...

20 answers found.

Answer 1400 (84.84848% helpful)

In Ubuntu 9.10:
1) cp /usr/share/slapd/DB_CONFIG /var/lib/ldap/
2) chown openldap.openldap /var/lib/ldap/DB_CONFIG
3) /etc/init.d/slapd restart
Permalink

Answer 932 (80.0% helpful)

Fedora release 9 (Sulphur)

cp /usr/share/doc/openldap-servers-2.4.10/DB_CONFIG.example /var/lib/ldap/DB_CONFIG 

chown ldap:ldap /var/lib/ldap/DB_CONFIG

service ldap restart

teo
Permalink

Answer 1267 (81.25% helpful)

Also for Fedora 11 x86_64 :
1). cp /usr/share/doc/openldap-servers-2.4.15/DB_CONFIG.example /var/lib/ldap/DB_CONFIG
2). chown ldap:ldap /var/lib/ldap/DB_CONFIG
3). service ldap restart 
Permalink

Answer 1923 (83.33333% helpful)

Check http://www.openldap.org/faq/data/cache/1072.html for directives.
Permalink

Answer 907 (68.75% helpful)

the Answer 4 is useful,thank you very much.in this solution ,DB_CONFIG.example is in the directory where your ldap intalled.and default is /etc/openldap,the /var/lib/ldap is the directory you had set in the file \'slapd.conf\'
Permalink

Answer 1984 (66.666664% helpful)

you might get this error if you didn't set the default directory path in slapd.conf (even if it's in /var/lib/ldap).
The error message is quite misleading because it explicitly state the directory path but doesn't actually appear to be looking at it...
(debian squeeze/ openldap 2.4.23)

Jules
Permalink

Answer 1887 (88.571434% helpful)

On RHEL 6.1: DB_CONFIG.example is located here:

/usr/share/openldap-servers/DB_CONFIG.example
Permalink

Answer 1853 (85.29411% helpful)

On CentOS 6:

cp /usr/share/doc/openldap-servers-2.4.19/DB_CONFIG.example /var/lib/ldap/DB_CONFIG
chown ldap:ldap /var/lib/ldap/DB_CONFIG
service slapd restart
Permalink

Answer 753 (88.33333% helpful)

Also for CentOS 5.2:

1) cp /etc/openldap/DB_CONFIG.example /var/lib/ldap/DB_CONFIG

2) chown ldap:ldap /var/lib/ldap/DB_CONFIG

3) service ldap restart
Note, you will get this warning:
    bdb_db_open: Recovery skipped in read-only mode. Run manual recovery if errors are encountered.
    config file testing succeeded

4) service ldap restart
And now there will be no errors.
Permalink

Answer 704 (50.0% helpful)

bdb_db_open: Recovery skipped in read-only mode. Run manual recovery if errors are encountered.
Permalink

Answer 1113 (50.0% helpful)

CentOs Solution works :)
Permalink

Answer 1266 (50.0% helpful)

Fedora 10 x86_64 worked...
cp /usr/share/doc/openldap-servers-2.4.12/DB_CONFIG.example /var/lib/ldap/DB_CONFIG
chown ldap:ldap /var/lib/ldap/DB_CONFIG
service ldap restart
Permalink

Answer 1697 (50.0% helpful)

Fedora 14 x86_64 works as well
Permalink

Answer 453 (88.23529% helpful)

Here is what resolved the issue for me on Redhat 5:

1) cp /etc/openldap/DB_CONFIG.example /var/lib/ldap/DB_CONFIG

2) chown ldap.ldap /var/lib/ldap/DB_CONFIG

3) /etc/init.d/ldap stop && /etc/init.d/ldap start
Note, you will get a bdb related warning the first time - it\'s safe to ignore.

4) Perform step 3 again and this time it will start up correctly with no errors or warnings.

cheers
-m
Permalink

Answer 1074 (33.333332% helpful)

Just Run bellow Command when you got this type of Problem....

#/usr/sbin/slapd_db_recover -v -h /var/lib/ldap/domain.com/

Regards
Ramakrishna Palla
Permalink

Answer 703 (0.0% helpful)

bdb_db_open: Recovery skipped in read-only mode. Run manual recovery if errors are encountered.
config file testing succeeded
Permalink

Answer 785 (0.0% helpful)

Good solution

Permalink

Answer 1053 (0.0% helpful)

FC11 works ... /usr/share/doc/openldap-servers ....
Permalink

Answer 1090 (0.0% helpful)

Nice Solutions

Anand Mane
Permalink

Answer 1036 (0.0% helpful)

the software could mention this itself, but what the heck. straight answer people need that thank you
Permalink

Add an answer/solution

If you know the answer, please add your own solution below.
If you don't know, but find out later, please come back and share your answer - there will be other people struggling with this too.


Please enter 61948 here

If you want to be notified via email when this is solved, enter your email address here:


Psst - want to help build a list of common error messages?
Put the following line in your /etc/[r]syslog.conf file:

*.emerg,*.alert,*.crit,*.err       @syslog.readthefuckingmanual.net

Collecting solutions to error messages since Aug 2005. © rtfm 2005-2021