On Fri, 2017-05-26 at 11:44 +0300, Alparslan Ozturk wrote: > dn: > cn=mhrsldap2-mhrsldap1,cn=replica,cn=dc\3Dsagliknet\2Cdc\3Dsaglik\2Cdc ... > nsds5replicareapactive: 0 > nsds5replicaLastUpdateStart: 20170522184536Z > nsds5replicaLastUpdateEnd: 19700101000000Z The answer is here: this replica has never been able to send a sucessful update to the ldap1 perhaps. You should check your error log, turn on replication logging, and generally check connectivity between these two masters, -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
