RE: Simple way to check that MMR is in sync?

["Borresen, John - 0442 - MITLL" <John.Borresen@ll.mit.edu>]

All,

I've been reading this string...

Comparing the entryCSNs & contextCSNs on both of my test servers at the base DN (dc=example,dc=ldap):

mm-server1:
entryCSN: 20140121153301.911487Z#000000#003#000000
contextCSN: 20140203183831.751838Z#000000#001#000000
contextCSN: 20140204143957.937393Z#000000#002#000000

mm-server2:
entryCSN: 20140121153301.911487Z#000000#003#000000
contextCSN: 20140129140325.443822Z#000000#000#000000
contextCSN: 20140203183831.751838Z#000000#001#000000
contextCSN: 20140129183014.073734Z#000000#002#000000
contextCSN: 20140121153301.911487Z#000000#003#000000

1) What is this information telling me?  (I want to be sure that I know)
2) Should I be concerned that there are more on mm-server2?

Thanks in advance
John

-----Original Message-----
From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Michael Ströder
Sent: Friday, February 07, 2014 2:11 PM
To: openldap-technical@openldap.org
Subject: Re: Simple way to check that MMR is in sync?

Ulrich Windl wrote:
> What about comparing the EntryCSN of the top-level object?

No! You should read what entryCSN attribute really is!

You have to compare the contextCSN values in the database's root entry.

In case you're using slapo-memberof or slapo-refint you want to have release
2.4.37+ with a fix for ITS#7710. Otherwise your admins will hate you for being
called at night for nothing.

> You could also slapcat each node, sort the lines and compare the results

Likely you don't want to do this for a directory with more than a few dozens
entries in a monitor check invoked every minute. ;-]

Ciao, Michael.