LDAP problems (was: High Gunnar,)

[misterbighh]

Here ist the next round. I found 2 doubles, but it was not the real solution for my problem and here is the result from the order.

 /usr/lib/openldap/slapd -u ldap -g ldap -F /etc/openldap/slapd.d -h 'ldaps:// ldap:// ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock' -d 256
@(#) $OpenLDAP: slapd 2.3.24 (Jul 27 2006 12:30:01) $
        @kagome:/var/tmp/portage/openldap-2.3.24-r1/work/openldap-2.3.24/servers/slapd
invalid config directory /etc/openldap/slapd.d, error 2
slapd stopped.
connections_destroy: nothing to destroy.

Now after a kolabconf I see this.

Sep 26 00:40:19 filmhost postfix/pickup[17006]: 3A6EF600F9: uid=10 from=<uucp>
Sep 26 00:40:19 filmhost postfix/cleanup[17021]: warning: dict_ldap_connect: Unable to bind to server ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=filmcom,dc=de: -1 (Can't contact LDAP server)
Sep 26 00:40:19 filmhost postfix/cleanup[17021]: warning: 3A6EF600F9: virtual_alias_maps map lookup problem for raf@gmx.de
Sep 26 00:40:19 filmhost postfix/pickup[17006]: warning: maildrop/BAF2B5FA01: Error writing message file
Sep 26 00:41:19 filmhost postfix/pickup[17006]: 3C5D1600F9: uid=10 from=<uucp>
Sep 26 00:41:19 filmhost postfix/cleanup[17021]: warning: dict_ldap_connect: Unable to bind to server ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=filmcom,dc=de: -1 (Can't contact LDAP server)
Sep 26 00:41:19 filmhost postfix/cleanup[17021]: warning: 3C5D1600F9: virtual_alias_maps map lookup problem for raf@gmx.de
Sep 26 00:41:19 filmhost postfix/pickup[17006]: warning: maildrop/BAF2B5FA01: Error writing message file
Sep 26 00:41:46 filmhost Error: Unable to connect to LDAP server `127.0.0.1:389'
Sep 26 00:41:46 filmhost Warning: Unable to read configuration data from LDAP

[misterbighh]

Just another log 

/usr/lib/openldap/slapd -u ldap -g ldap -h 'ldaps:// ldap://' -d 256
@(#) $OpenLDAP: slapd 2.3.24 (Jul 27 2006 12:30:01) $
        @kagome:/var/tmp/portage/openldap-2.3.24-r1/work/openldap-2.3.24/servers/slapd
bdb_db_open: unclean shutdown detected; attempting recovery.
bdb(dc=filmcom,dc=de): unrecognized name-value pair: set
bdb_db_open: Database cannot be recovered, err 22. Restore from backup!
bdb(dc=filmcom,dc=de): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
bdb(dc=filmcom,dc=de): txn_checkpoint interface requires an environment configured for the transaction subsystem
bdb_db_close: txn_checkpoint failed: Invalid argument (22)
backend_startup_one: bi_db_open failed! (22)
bdb_db_close: alock_close failed
slapd stopped.
connections_destroy: nothing to destroy.

[Gunnar Wrobel]

As the ldap server tells you your db is corrupt. You may be lucky and

Code:

cd /var/lib/openldap-data
db4.2_recover

repairs the database. But there is also a good chance that this won't work. In that case you would need to revert to your backup of the data.

This is actually the second time during a short period that I see that ldap destroys its own db. Hope this will not occur more often with the new ldap version now.

[misterbighh]

And the funny thing is, there is no a db, cause I

[Gunnar Wrobel]

I don't know what this forum does to your browser but every second answer is lost. Ever thought about using the Internet Explorer?

[misterbighh]

I use Firefox. Hm, I try your updates and the result is the same.

[Gunnar Wrobel]

The ebuild update should only fix the slapd.conf.template problem. This was a problem introduced in upstream cvs (https://www.intevation.de/roundup/kolab/issue1426).

Nevertheless this will not fix your ldap db. If you were unable to recover the db you will need to remove the /var/lib/openldap-data directory and recreate the db.

[misterbighh]

High Gunnar, now I have realized that openldap is included in a stage3 (2006.1)  Do you sure that this circumstances is not the reasen for troublemaking if I

[Gunnar Wrobel]

I'm sorry for the mess. I did simply include the upstream CVS changes from the kolab project and there was another problem in there. I'll fix that today and issue another bug upstream.

And there will also be a change in the development scheme. The current dev packages will get masked until new changes have run through complete internal testing. This should reduce the likelihood of hickups like this one.

Cheers,

Gunnar

[misterbighh]

I make your updates, but the rusult is the same. Sorry for you and for me Next step is to make a fresh install and after that I wil give you a message.

[Gunnar Wrobel]

I doubt you were able to run kolabconf in case your ldap server does not start.

Fix your /var/lib/openldap-data/DB_CONFIG file as specified in this bug report:

https://www.intevation.de/roundup/kolab/issue1428

This should allow you to fire up slapd which will then enable you to run kolabconf and fix your configurations.

Cheers,

Gunnar