Wendt, Trevor wrote:
######################
"The generation ID errors sound like real errors, but those should be
resolvable with the correct replica re-initialization done."
I've tried re-initializing the consumer multiple times with no success.
The NSMMReplicationPlugin - replica_check_for_data_reload and the "csn"
errors are on my supplier server. When my srv2 went offline my srv1
became the "Master" so I can't go from srv2 to srv1 without losing
entries. This is the dilemma...
Thanks for you're suggestions. Please, keep them coming.
######################
Can you show us the RUV from the server that produces the csnplCommit error?
ldapsearch -x -D "cn=directory manager" -W -s base -b
"nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=<mydomain>,dc=com"
"(&(objectclass=*)(objectclass=nstombstone))"
And your replica configuration?
ldapsearch -x -D "cn=directory manager" -W -b "cn=config"
"(objectclass=nsds5replica)"
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
