Replication slapd: slurpd

Bonjour,

je met en place une replication pour mon serveur LDAP grace a slurpd, mais j'ai quelques problemes lors de la replication apparement. J'ai suivi des tutoriels pour mettre la replication en place, mais la database de mon serveur secondaire ne se met pas a jour...
je vous joins mon fichier de config, peut etre quelqu'un trouvera-t-il ce qui cloche....

#
# /etc/openldap/slapd.conf <-- LDAP Server configuration file
#
include         /etc/openldap/schema/core.schema
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/inetorgperson.schema
include         /etc/openldap/schema/nis.schema
include         /etc/openldap/schema/redhat/autofs.schema

pidfile         /var/run/openldap/slapd.pid
argsfile        /var/run/openldap/slapd.args

# The next three lines allow use of TLS for encrypting connections using a
# dummy test certificate which you can generate by changing to
# /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on
# slapd.pem so that the ldap user or group can read it.  Your client software
# may balk at self-signed certificates, however.
TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
TLSCertificateFile /etc/pki/tls/certs/slapd.pem
TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem

# 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

disallow bind_anon
access to *
        by dn="cn=Manager,dc=lab" write
        by dn="cn=replicationagent,ou=profiles,dc=lab" write
        by dn="cn=proxyagent,ou=profiles,dc=lab" read
        by self write
        by anonymous auth
        by users read
access to dn.subtree="ou=people,dc=lab"
        by dn="cn=Manager,dc=lab" write
        by dn="cn=replicationagent,ou=profiles,dc=lab" write
        by dn="cn=proxyagent,ou=profiles,dc=lab" read
        by users write

#######################################################################
# ldbm and/or bdb database definitions
#######################################################################

database        bdb
suffix          "dc=lab"
rootdn          "cn=Manager,dc=lab"
rootpw          {SSHA}c+ePmdHcx0NUBeOH6bEMfR8uB1Ui+U4D

# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory       /var/lib/ldap

# Replica configuration (on the master server)
replogfile /var/lib/ldap/replica/replication.log
replica uri=ldaps://192.168.100.95:636/
        binddn="cn=replicationagent,ou=profiles,dc=lab"
        bindmethod=simple credentials=replicate

# Replica configuration (on the slave server)
#updatedn "cn=replicationagent,ou=profiles,dc=lab"
#updateref "ldaps://192.168.100.93:636"

# Indices to maintain for this database
index objectClass                       eq,pres
index ou,cn,mail,surname,givenname      eq,pres,sub
index uidNumber,gidNumber,loginShell    eq,pres
index uid,memberUid                     eq,pres,sub
index nisMapName,nisMapEntry            eq,pres,sub
index uniqueMember                      eq

# DB_CONFIG settings - For SleepyCat Berkeley DB
dbconfig set_cachesize 0 10485760 0
dbconfig set_lg_regionmax 262144
dbconfig set_lg_bsize 2097152

le fichier est le meme sur le serveur secondaire (avec la partie replica primaire commente et la partie replica secondaire non-commentee) et la database a ete copie au prealable grace a slapcat/slapadd. De plus, mon dossier et son contenu /var/lib/ldap/replica possede les droits 600 pour l'utilisateur ldap:ldap.
Lorsque je fais un "ldapsearch" apres avoir ajoute un nouvel utilisateur, le serveur primaire trouve correctemnt les infos alors que le serveur secondaire cense recevoir la mise a jour continue de m'afficher les infos de la base quand je l'ai repliquee manuellement (slapcat/slapadd).

Merci d'avance pour toute aide
Toeic