Hello list.
I have two openldap servers 2.4.23 running in a multimaster setup whose
content diverged at some point. Fortunatly, I had different backup files
for both, which allowed to me to reconciliate content manually. I
reimported the resulting ldif file in one of the server, re-exported it
through slapcat, and reimported it in the other server, after dropping
all existing databases (including acceslog one).
However, I end up with two bases with multiple and divergent contextCSN
values:
contextCSN: 20120420144311.217351Z#000000#000#000000
contextCSN: 20120903132738.849382Z#000000#001#000000
contextCSN: 20120903132426.927826Z#000000#002#000000
contextCSN: 20120420144311.217351Z#000000#000#000000
contextCSN: 20120903132426.925966Z#000000#001#000000
contextCSN: 20120903132924.793560Z#000000#002#000000
Any attempt to manually reduce this to a single value in the backup file
before restoration ended in infinite refresh request from the second
servers and "stale cookie" error messages.
So, my questions are:
- is this an expectable state to have multiple values for contextCSN ?
- does it hurt, beyond making synchronisation checking almost impossible ?
- how to return to a stable situation ?
I can't change ldap version easily, and I'd rather return to classic
master-slave setup if the problem is not fixable otherwise.
--
BOFH excuse #213:
Change your language to Finnish.
