Glad you got it working Herb!
Looks like we need to improve some replication logging.
Cheers,
Mark
On 04/23/2012 01:06 PM, Herb Burnswell wrote:
Russ and Mark thank you for your suggestions.
I finally managed to get replication working... After simplifying to
just working on the dual master
Russ and Mark thank you for your suggestions.
I finally managed to get replication working... After simplifying to just
working on the dual masters A & B and still seeing the same error, a dug
more into something that Rich said previously.
He mentioned that the password (nsDS5ReplicaCredentials)
Hi Herb,/
/While working on a different replication issue I accidentally
reproduced your issue. My issue was a typo in the password in the repl
agreement. I know you said you passwords were the same, but maybe there
is still a mismatch. Also, if the root dn specified in the agreement
doesn
On Apr 20, 2012, at 3:24 PM, Herb Burnswell wrote:
> 4. Run an initialization from the DS console on master B to master A.
I'm still pretty new to 389, but when learning about setting up replication
agreements I remember specifically that initialization is done only one way.
The replication ag
Hi All,
I wanted to update this issue as I've made some progress but replication is
still not working as it should. I've removed the previous communication as
it was getting very long and I began to receive 'message too large'
responses from the list server. The history of this post can be read
has not been
>> working for several years) the systems will all replicate to the most
>> recent information. Correct?
>> >>>>I think that's the tricky part. Make sure you backup your directory
>> on all
>> >>>>the LDAP first so you hav
02/2012 05:48 PM, Herb Burnswell wrote:
-- Forwarded message --
From: Rich Megginson
Date: Mon, Apr 2, 2012 at 3:23 PM
Subject: Re: [389-users] Repair replication
To: "General discussion list for the 389 Directory server project." <
389-users@lists.fedoraproject.org>
would be greatly appreciated.
Thanks in advance,
Herb
--
Message: 2
Date: Thu, 22 Mar 2012 10:40:34 -0400
From: Chun Tat David Chu mailto:beyonddc.stor...@gmail.com>>
To: "General discussion list
hat system B has not been running for some time, ideally
> it would simply replicate to the current data on system A. After
> replication is reestablished the systems are set up to "Always keep
> directories in sync". If anyone can confirm the behavior that will occur
> up
Hi All,
I'm new to LDAP administration and have been tasked with fixing the system
replication of 4 Linux systems running Fedora Directory Services. I am
very comfortable working with Linux/Unix but am not experienced with LDAP.
I've been reading the communications from this user group and readin
10 matches
Mail list logo
