Hi all, I have upgraded to 2.4.36 openLDAP version. The problem still exists. It seem to be appear less than before. This week this problem occur only once.
To resolve this problem i'm doing: stop slapd on ldap that haven't entry and launch it with /usr/local/openldap/libexec/slapd -c rid=201,dsn=20131003140020.844217Z#000000#002#000000 -h "ldap://:389 ldaps://:636" -F /usr/local/openldap/etc/openldap/slapd.d -u ldap -g ldap -l local4 rid number is my source syncrepl dsn is 20 seconds before the problem ( retrieve from entryCSN in question ) is't the good way to do 2013/9/24 Aaron Richton <[email protected]> > On Tue, 24 Sep 2013, Lanfeust troy wrote: > > I understand that but before post my message i read openldap release note >> but i can't see something related to my problem. >> > > [which is] > > > do_syncrep2: rid=102 CSN too old, ignoring >> 20130923090023.266239Z#000000#**002#000000 >> >> @(#) $OpenLDAP: slapd 2.4.33 (....) >> > > > So you're running MMR and seeing issues about "old" CSNs and don't see the > potential relevance of a change log that references: > > Fixed slapd syncrepl updateCookie status (ITS#7531) > Fixed slapd syncrepl for old entries in MMR setup (ITS#7427) > > ...maybe they're your issue, maybe they're not, but in the amount of time > you need to simply read this you could find a 2.4.36 package. >
