Here are a couple of examples. I do not believe that these coincide with the replication failures, but I will able to verify tomorrow during my maintenance window. No these are live entries. [24/Jan/2013:07:03:32 -0500] - dn2entry_ext: the dn "uid=aalberti01,ou=portalusers,dc=nationaldcp,dc=net" was in the entrydn index, but it did notexist in id2entry of instance userRoot. [24/Jan/2013:08:42:45 -0500] - dn2entry_ext: the dn "uid=wearly,ou=portalusers,dc=nationaldcp,dc=net" was in the entrydn index, but it did not exist in id2entry of instance userRoot. [24/Jan/2013:08:43:59 -0500] - dn2entry_ext: the dn "uid=wearly,ou=portalusers,dc=nationaldcp,dc=net" was in the entrydn index, but it did not exist in id2entry of instance userRoot. Santos U. Ramirez Linux Systems Administrator National DCP, LLC 150 Depot Street Bellingham, Ma. 02019 Phone: 508-422-3089 Fax: 508-422-3866 From: Rich Megginson [mailto:rmeggins@xxxxxxxxxx] On 01/30/2013 11:49 AM, Santos Ramirez wrote: We have found several instance of this error : XXXX was in the entrydn index, but it did not exist in id2entry of instance userRoot
Santos U. Ramirez Linux Systems Administrator National DCP, LLC 150 Depot Street Bellingham, Ma. 02019 Phone: 508-422-3089 Fax: 508-422-3866 From: Santos Ramirez Excellent I will be in touch soon. Thank you once again. Santos U. Ramirez Linux Systems Administrator National DCP, LLC 150 Depot Street Bellingham, Ma. 02019 Phone: 508-422-3089 Fax: 508-422-3866 From: Rich Megginson [mailto:rmeggins@xxxxxxxxxx] On 01/30/2013 10:28 AM, Santos Ramirez wrote: Hi Rich, We are running RHEL 5.8 389-ds-base-1.2.10.14-1.el5 We do not see any errors in the logs .
Santos U. Ramirez Linux Systems Administrator National DCP, LLC 150 Depot Street Bellingham, Ma. 02019 Phone: 508-422-3089 Fax: 508-422-3866 From: Rich Megginson [mailto:rmeggins@xxxxxxxxxx] On 01/30/2013 10:00 AM, Santos Ramirez wrote: Good Morning, We have a master – master replication agreement. When we initialize the replication it works perfectly we can see changes to a test user we have set up go up and down from the two servers. However at some point the replication stops and we cannot get replication to start once again. The only way we can get replication to start once again is to recreate the replication agreement and then it fails again. Can anyone please point us in a direction. I am relatively new to 389 so any help would be greatly appreciated. What platform? Santos U. Ramirez Linux Systems Administrator National DCP, LLC 150 Depot Street Bellingham, Ma. 02019 Phone: 508-422-3089 Fax: 508-422-3866 This email and any attachments are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, do not copy or forward to any unauthorized persons, permanently delete the original and notify the sender by replying to this email. -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
