Kolab2 Slapd hanging - master/slave replication issues

[Dieter Kluenter]

Hi Martin,

Martin Konold <martin.konold at erfrakon.de> writes:

> Am Dienstag, 15. März 2005 09:08 schrieb Dieter Kluenter:
> 
> Hi Dieter,
> 
> > A database corruption occurs only with heavy write load and
> > insufficiened cache size or a flag DB_TXN_NOSYNC set in DB_CONFIG.
> 
> Please provide me with more insight. Are there any configuration options we 
> shall change in our remplates before releaseing Kolab2 final? 
> 
> I am especially interested in option which increase the reliability and 
> scalability.

Just an initial hint, compile openldap with --enable-local=yes,
--enable-monitor=yes, start slapd with -h "ldap:/// ldapi:///" , chmod 777
/kolab/var/run/ldapi and configure local clients to connect to slapd via local
socket, that is "ldapi://%2Fkolab%2Fvar%2Frun%2Fldapi".
Include a 'database monitor" declaration in slapd.conf.
Copy sample DB_CONFIG from the openldap source package
(servers/slapd/DB_CONFIG) to the database directory.

-Dieter 

-- 
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:01443B53