Re: Naming conflict on hub/consumer

[Colin Tulloch <Colin.Tulloch@xxxxxxxxxxx>]

RHDS 9.1

389-ds-base-1.2.11.15-30.el6_5.x86_64

 

From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Rich Megginson
Sent: Tuesday, January 21, 2014 11:55 AM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Naming conflict on hub/consumer

 

On 01/21/2014 10:47 AM, Colin Tulloch wrote:

Hi All –

 

We had a bundle of problems with our MM/consumer setup.  Ran of out FDs on the consumers, had the slapd process on a master die, etc.

Platform?  389-ds-base version?  rpm -q 389-ds-base

 

We’re getting things back up and running properly, but having some replication issues now.  We’ve got it mostly cleaned up – the masters are in sync, and all consumers but 1 hub.

 

However, 1 hub has 3 naming conflicts on an entry.  How can we resolve these?  Since it’s read-only, the normal documented processes won’t work of course.  The non-conflicted entry isn’t receiving updates from the masters.  We use the directory for PKI, and the entry contains a CRL that is going to expire – not good.

 

Do we need to just wait, and the actual entry will get updated at some point?  With the errors we had, it seemed to take a long time for the directories to replicate around and catch up.

--

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