Syncrepl Problem after repeatedly reboot

HRZ Konten <[email protected]>
Newsgroups gmane.network.openldap.general
Message-ID <[email protected]>
Hallo all,

we have 2 OpenLDAP 2.4.17 with  N-Way Replication on Debian Lenny.

Config
dn: olcDatabase={0}config
objectClass: olcDatabaseConfig
olcDatabase: {0}config
olcRootPW:: xxxxxxxxxxxxxxxxx
structuralObjectClass: olcDatabaseConfig
entryUUID: 446a8178-95f7-102e-8e9a-95c863b9a1ce
creatorsName: cn=config
createTimestamp: 20100115075644Z
olcSyncrepl: {0}rid=001 provider=ldaps://xxxxxxxxxxxxxxxx:636/ bindd
 n="cn=config" bindmethod=simple credentials=xxxxxxxxxxxxxxxxxxx
searchbase="cn=confi
 g" type=refreshAndPersist retry="5 5 300 +" schemachecking="on" timeout=3
olcSyncrepl: {1}rid=002 provider=xxxxxxxxxxxxxxxxxxxxxxxxxxx:636/ bindd
 n="cn=config" bindmethod=simple credentials=xxxxxxxxxxxxxxxx
searchbase="cn=confi
 g" type=refreshAndPersist retry="5 5 300 +" schemachecking="on" timeout=3
olcMirrorMode: TRUE
entryCSN: 20100115075655.626787Z#000000#000#000000
modifiersName: cn=config
modifyTimestamp: 20100115075655Z

We reboot one of the nodes a couple of times at the time as the other
node made ~ 60 000 adds.
After 12 hours there is still some difference between both nodes:

root@ldap1:~# ldapsearch -D "cn=manager,dc=xxx" -W -x -b "dc=xxx"
courseOfStudy=* | grep courseOfStudy | wc -l
Enter LDAP Password:
61125

root@ldap2:~# ldapsearch -D "cn=manager,dc=xxx" -W -x -b "dc=xxx"
courseOfStudy=* | grep courseOfStudy | wc -l
Enter LDAP Password:
47366

The contextCSN is equal on both nodes:

ldap1: 
ldapsearch -xLLLH ldaps://ldap1:636 -s base -b "dc=xxx" contextCSN -W -D "cn=manager,xxx"
Result:
contextCSN: 20100121183644.034011Z#000000#000#000000

ldap2: 
ldapsearch -xLLLH ldaps://ldap2:636 -s base -b "dc=uxxx" contextCSN -W -D "cn=manager,xxx"
Result:
contextCSN: 20100121183644.034011Z#000000#000#000000


Is there an easy way to force a new replication on the second node?
I will really appreciate your help...
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.