[Kolab-devel] Kolab Server 2.0.1 RC 1 released

[Richard Bos]

Op dinsdag 9 augustus 2005 12:43, schreef Bernhard Herzog:
> Please test this release and report your experiences with it, so that we
> know how well it works for you.

Bad experience:
Excellent all required Ports are available!
LDAP repository is empty - assuming fresh install
............
prepare LDAP database...
temporarily starting slapd
Waiting for OpenLDAP to start
could not connect ldap server ldap://127.0.0.1:389/ at /kolab/etc/kolab/kolab_bootstrap line 415.

   414     my $ldapuri = URI->new($ldap_uri) || die "error: could not parse given uri";
   415     my $ldap = Net::LDAP->new($ldap_uri, verify => 'none' ) || die "could not connect ldap server $ldap_uri";
  
I have:
install perl-kolab-5.8.7-2.0_20050727
install kolabd-1.9.4-20050801
install kolab-webadmin-0.4.0-20050728
install kolab-resource-handlers-0.3.9-20050727
INSTALL: openpkg-2.4.2-2.4.2 ........  perl-kolab-5.8.7-2.0_20050727
 kolabd-1.9.4-20050801 kolab-webadmin-0.4.0-20050728
 kolab-resource-handlers-0.3.9-20050727
MISSSRC: none
MISSPKG: none
MISSING: none
SURPLUS: none
SUMMARY: NODE=atlas; CMD=kolab; DATE=2005-08-09/19:08:29; HASX11=; DONE

Kolab-2.0 used to run before on the same machine.  Don't worry nothing operation fortunately.

Running openldap with debugging on results in:
@(#) $OpenLDAP: slapd 2.2.27 (Aug  9 2005 17:25:42) $
        kolab at atlas:/opt/kolab/RPM/TMP/openldap-2.2.27/servers/slapd
daemon_init: ldap://127.0.0.1:389/
bdb_db_init: Initializing BDB database
bdb_db_open: dc=school,dc=nl
bdb(dc=school,dc=nl): Ignoring log file: /kolab/var/openldap/openldap-data/log.0000000001: magic number 0, not 40988
bdb(dc=school,dc=nl): Invalid log file: log.0000000001: Invalid argument
bdb(dc=school,dc=nl): PANIC: Invalid argument
bdb(dc=school,dc=nl): PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
bdb_db_open: dbenv_open failed: DB_RUNRECOVERY: Fatal error, run database recovery (-30978)
backend_startup: bi_db_open failed! (-30978)
bdb(dc=school,dc=nl): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
bdb(dc=school,dc=nl): txn_checkpoint interface requires an environment configured for the transaction subsystem
bdb_db_destroy: txn_checkpoint failed: Invalid argument (22)
slapd stopped.
connections_destroy: nothing to destroy.


What can to do now?


-- 
Richard Bos
Without a home the journey is endless