ok, this appears to be user error. Sorry.
i am still curious if this only need be done on replicated masters and not the
read-only replicas or must this be configured on all servers.
thanks!
/mrg
On Apr 14, 2014, at 14:22, Michael R. Gettes wrote:
> I am using 389-Directory/1.2.11
389-Directory/1.2.11.15 B2013.238.2155
Nothing in errors, nothing in access log files
uname -a
Linux 2.6.32-358.18.1.el6.x86_64 #1 SMP Fri Aug 2 17:04:38 EDT 2013 x86_64
x86_64 x86_64 GNU/Linux
yum list | grep 389
389-admin.x86_64 1.1.29-1.el6 @epel-x86_64-server-6
Given your scenario - if you did a restore then you would get an error message
of something like
NSMMReplicationPlugin - agmt="cn=master-t01-to-master-t02"
(ldap-master-t02:389): Replica has a different generation ID than the local
data.
Yes, I just did this. Then you would want to conduct an
It worked and without a restart of the server. THANKS!
/mrg
On Mar 20, 2012, at 10:32, Rich Megginson wrote:
> On 03/14/2012 07:25 PM, Michael R. Gettes wrote:
>> EL 5.6 and ds-389 1.2.9.9
>>
>> I have a question of curiosity…
>>
>> I have a number of r
It WAS on 1.2.8.3 but since you guys helped me to get to 1.2.9.9 - the problem
is now fixed!
once again, THANK YOU!
/mrg
On Mar 6, 2012, at 9:23, Rich Megginson wrote:
> On 02/15/2012 07:15 PM, Michael Gettes wrote:
>>
>> My global time limit is 3600. global idle timeout is 0. global size l
On Mar 2, 2012, at 9:21, Rich Megginson wrote:
> On 03/01/2012 09:56 PM, Michael R. Gettes wrote:
>> I am in process of standing up a new directory service and will have to
>> migrate many apps to the new service. Do you believe 1.2.10.2 is stable
>> enough for productio
Ah! Okay, that helps! Sorry for being dense.
BUT, now I download the epel-389-ds-base.repo into the yum.repos.d and I get:
[root@localhost SRPMS]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
[root@localhost SRPMS]# yum install 389-ds
Loaded plugins: katello, p
