Just restarting slapd on both master/slave could help. You also could
detect miss-synchronized entries using
. This script also
have a "touch" feature to try to force resync. Otherwise, try to enable
sync loglevel to debug. Finally, it's also could be faster to
dump/restore from master to slave and after check synchronization works.
Le 30/11/2021 à 16:57, Enrico Weigelt, metux IT consult a écrit :
I've encountered my slaves (Zimbra cluster) aren't fully in sync with
master. Some entries are missing attributes. Maybe it's a fallout from
previous errors in my MMR setup (several minutes clocks difference, so
one master couldn't sync to another).
* modifying an affected entry doesn't fix it, just changes the
actually changed attributes (delta-sync ?)
* starting the slave w/ -c 'rid=100,csn=0' showed lots of corresponding
log traffic (on first start), but still tells the entries were equal,
doesn't fix the entries
* problem: I don't know which entries are affect, just found a few
Can anyone give me a hint on how to do a full resync ?
Benjamin Renard - Easter-eggs
44-46 rue de l'Ouest - 75014 Paris - France - Métro Gaité
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 43 35 00 76
mailto:email@example.com - http://www.easter-eggs.com