Hi! I have checked the replication verification a little bit more. First of all. I'm using 2.4.21 and you need to allow reading to both cn=monitor and cn=config. So using a monitoring user is important here. My slapd.conf configuration: # syncrepl Provider for primary db overlay syncprov syncprov-checkpoint 5 1 # syncrepl directive syncrepl rid=001 provider=ldap://host2 bindmethod=simple binddn="cn=Manager,dc=domain,dc=com" credentials=secret searchbase="dc=domain,dc=com" schemachecking=on type=refreshAndPersist retry="60 +" mirrormode on # enable monitoring database monitor # allow onlu rootdn to read the monitor access to * by dn.exact="cn=CNMonitor User,dc=domain,dc=com" read by * none # enable monitoring database config # allow onlu rootdn to read the monitor access to * by dn.exact="cn=CNMonitor User,dc=domain,dc=com" read by * none And the replication must update the contextCSN attribute. You can verify this by: ldapsearch -x -h <host> -D "<monitoring user>" -W -s base -b "dc=domain,dc=com" contextCSN In my example the result is: dn: dc=domain,dc=com contextCSN: 20100823161844.565867Z#000000#000#000000 contextCSN: 20100825160932.333710Z#000000#001#000000 Hope this helps. So as long as you can retrieve this information using the same monitoring user as configured in CN=Monitor you should retrieve replication verification info. Regards - Andreas On Jan 26, 2011, at 10:30 PM, Peter Boosten wrote:
|