I'm bumping into an issue with referential integrity using 389-ds-base-1.2.11.15 on RHEL 6.4 and multi-master replication and seeking clarification.
I have three servers configured for three-way multi-master replication: ds1, ds2, ds3. The admin guide for directory server 8.2 seems to recommend only enabling referential integrity on a single producer, so I have enabled referential integrity on ds1. When I perform a modrdn on ds1, referential integrity kicks in, and the change is replicated. When perform a modrdn on ds2 or 3, the modrdn works, but it never tickles referential integrity on ds1.
Should I really be enabling referential integrity on all the masters, or is there something else that I'm missing?
On a semi-related note, on ds1, where referential integrity is enabled and occurring, I've noticed that nsslapd-pluginEnabled is set to 'off' in the running directory server, even though referential integrity is working, and it is set to 'on' in dse.ldif. Has anyone seen this behavior?
Thanks,
Casey
--
---------------------------------------------
Casey Feskens <cfeskens@xxxxxxxxxxxxxx>
Assistant Director of Systems Services
Willamette Integrated Technology Services
Willamette University, Salem, OR
---------------------------------------------
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
