On 03/08/2017 11:39 AM, Christopher Young wrote:
> My replication scheme has things like so:
>
> orldc-prod-ipa01 <--> orldc-prod-ipa02 <--> bohdc-prod-ipa01
>
> I had run re-initialize on orldc-prod-ipa02 (--from orldc-prod-ipa01) AND
> re-initialize on bohdc-prod-ipa01 (--from
My replication scheme has things like so:
orldc-prod-ipa01 <--> orldc-prod-ipa02 <--> bohdc-prod-ipa01
I had run re-initialize on orldc-prod-ipa02 (--from orldc-prod-ipa01) AND
re-initialize on bohdc-prod-ipa01 (--from orldc-prod-ipa02).
That is where i'm currently at with the same errors.
Any
On 03/07/2017 06:08 PM, Christopher Young wrote:
> I had attempted to do _just_ a re-initialize on orldc-prod-ipa02
> (using --from orldc-prod-ipa01), but after it completes, I still end
> up with the same errors. What would be my next course of action?
I have no idea. Sounds like the reinit
I had attempted to do _just_ a re-initialize on orldc-prod-ipa02
(using --from orldc-prod-ipa01), but after it completes, I still end
up with the same errors. What would be my next course of action?
To clarify the error(s) on orldc-prod-ipa01 are:
-
Mar 7 18:04:53 orldc-prod-ipa01 ns-slapd:
On 03/07/2017 11:29 AM, Christopher Young wrote:
> Thank you very much for the response!
>
> To start:
>
> [root@orldc-prod-ipa01 ~]# rpm -qa 389-ds-base
> 389-ds-base-1.3.5.10-18.el7_3.x86_64
>
You are on the latest version with the latest replication fixes.
>
> So, I believe a good
Thank you very much for the response!
To start:
[root@orldc-prod-ipa01 ~]# rpm -qa 389-ds-base
389-ds-base-1.3.5.10-18.el7_3.x86_64
So, I believe a good part of my problem is that I'm not _positive_
which replica is good at this point (though my directory really isn't
that huge).
Do
What version of 389-ds-base are you using?
rpm -qa | grep 389-ds-base
comments below..
On 03/06/2017 02:37 PM, Christopher Young wrote:
> I've seen similar posts, but in the interest of asking fresh and
> trying to understand what is going on, I thought I would ask for
> advice on how best to
On 09/21/2016 11:43 AM, Rob Crittenden wrote:
> Ian Harding wrote:
>> I used to have a lot of replicas, but like a house of cards, it all came
>> crashing down.
>>
>> I was down to two, that seemed to be replicating, but last few days I've
>> noticed that they haven't always been.
>>
>>
Ian Harding wrote:
I used to have a lot of replicas, but like a house of cards, it all came
crashing down.
I was down to two, that seemed to be replicating, but last few days I've
noticed that they haven't always been.
freeipa-sea.bpt.rocks is where we do all our admin.
seattlenfs.bpt.rocks is
Hi Thierry,
Thanks for the reply.
Turned out that the slapi-plugin was not ignoring the replicated
operations. Problem solved.
Regards.
--Prashant
On 6 April 2015 at 23:25, thierry bordaz tbor...@redhat.com wrote:
Hello Prashant,
If you are able to reproduce the problem (ipasshpubkey not
On 04/07/2015 10:51 AM, Prashant Bapat wrote:
Hi Thierry,
Thanks for the reply.
Turned out that the slapi-plugin was not ignoring the replicated
operations. Problem solved.
Great news !
regards
thierry
Regards.
--Prashant
On 6 April 2015 at 23:25, thierry bordaz tbor...@redhat.com
Hello Prashant,
If you are able to reproduce the problem (ipasshpubkey not
replicated), would you enable replication and plugin logging
(http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#Troubleshooting)
and provide the access/errors logs ?
thanks
thierry
On
12 matches
Mail list logo
