389-users December 2012

389-users@lists.fedoraproject.org

26 participants
26 discussions

creating replication user from 389-console
by Sharuzzaman Ahmat Raslan 10 Dec '12

10 Dec '12

Hi all, According to RH document, if you want to create the replication user, you must edit the dse.ldif file and put the user information there. I tried to use 389-console, create user (which use uid=repman) then try to enable cn=repman, but there is error saying that directory server refuse to do the renaming. What is the correct way to create cn=repman only by using 389 console? Thanks. https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0… -- Sharuzzaman Ahmat Raslan

4 9

RUV is not getting updated for both Master and consumer
by Das, Jyoti Ranjan (STSD) 10 Dec '12

10 Dec '12

Hi, Ruv is not getting updated properly when changing the replica role from the Admin server GUI. Please find the reproducer details below. Step-1: Create two instances named as INST1 and INST2 Step-2: Register the above two instances with the Admin server Step-3: Assign the Hub role to INST1 from the admin server GUI. Configuration tab -> replication -> userRoot -> enable the replication and assign the HUB role -> Save Step-4: Assign the consumer role to INST2 from the admin server GUI. Configuration tab -> replication -> userRoot -> enable the replication and assign the consumer role -> Save Step-5: Change the role for INST1 from Hub to Master from Admin Server GUI. Configuarion tab-> replication -> userRoot > enable the Single Master check box and provide the appropriate replica id -> Save Check the RUV RUV: ===== dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=asiapacific,dc=hpqcorp,dc=net objectClass: top objectClass: nsTombstone objectClass: extensibleobject nsds50ruv: {replicageneration} 50b5024c0000ffff0000 dc: asiapacific ===== Step-6: Create a replication agreement between the INST1 and INST2. Checked the RUV.There is no change here in the RUV RUV: ===== dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=asiapacific,dc=hpqcorp,dc=net objectClass: top objectClass: nsTombstone objectClass: extensibleobject nsds50ruv: {replicageneration} 50b5024c0000ffff0000 dc: asiapacific ===== Step-7: Add an entry to the INST1 and check the RUV RUV in INST1: ====== dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=asiapacific,dc=hpqcorp,dc=net objectClass: top objectClass: nsTombstone objectClass: extensibleobject nsds50ruv: {replicageneration} 50b5024c0000ffff0000 nsds50ruv: {replica 65535 ldap://dirsrv12.asiapacific.hpqcorp.net:2<http://dirsrv12-virtualbox.asiapacific.hpqcorp.net:2/> 389} 50b506150000ffff0000 50b506150000ffff0000 dc: asiapacific nsruvReplicaLastModified: {replica 65535 ldap://dirsrv12.asiapacifi c.hpqcorp.net:2389<http://c.hpqcorp.net:2389/>} 50b50615 As you can see here, RUV in the INST1 which is a supplier is having the replica id 65535 even after given a proper id during role change and below in the INST2 RUV which is a consumer here it's max CSN is not getting updated in the RUV. Could you please give your insight to this problem?. Please note that it is being reproduced in the latest version of 389 directory server i.e. 1.2.15 RUV in INST2: ======== dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=asiapacific,dc=hpqcorp,d c=net objectClass: top objectClass: nsTombstone objectClass: extensibleobject nsds50ruv: {replicageneration} 50b5024c0000ffff0000 nsds50ruv: {replica 65535 ldap://dirsrv12.asiapacific.hpqcorp.net:2<http://dirsrv12-virtualbox.asiapacific.hpqcorp.net:2/> 389} 50b506150000ffff0000 dc: asiapacific nsruvReplicaLastModified: {replica 65535 ldap://dirsrv12.asiapacifi c.hpqcorp.net:2389<http://c.hpqcorp.net:2389/>} 50b50616 Regards, Jyoti

1 0

sync nsaccountlock - userAccountControl
by Adriano Matos Meier 05 Dec '12

05 Dec '12

Dear, replication 389 -> AD (onewaysync) is working, but would like to replicate the account lockouts in 389 (nsaccountlock = true) for AD (userAccountControl = 514). Is possible? Any suggestions? Thank's. -- ------------------------------------------------------------------------ *Adriano Matos Meier Unidade de Tecnologia da Informação Sistema FIESC* Rod. Admar Gonzaga, 2765 - Itacorubi - 88034-001 - Florianópolis - SC Fone (48) 3239-1418 - e-mail: matos(a)sc.senai.br site: http://www.sistemafiesc.org.br

2 1

RUV is not getting updated for both Master and consumer
by Das, Jyoti Ranjan (STSD) 05 Dec '12

05 Dec '12

1 0

Re: [389-users] official supported way for multi master replication
by Derek Belcher 05 Dec '12

05 Dec '12

Depending on your 389-ds version, for me the Red Hat 9.0 manual helped me set up my mmr environment. -Derek From my HTC Sensation 4G on T-Mobile. The first nationwide 4G network ----- Reply message ----- From: "Chandan Kumar" <chandank.kumar(a)gmail.com> To: "General discussion list for the 389 Directory server project." <389-users(a)lists.fedoraproject.org> Subject: [389-users] official supported way for multi master replication Date: Wed, Dec 5, 2012 12:57 am Hi Your best friend is the redhat Manuals. That mmr script did not work for me either. Below link I find helpful. http://wiki.nikoforge.org/Setup_of_Centos_Directory_Server_Read-Write_Repli… On Dec 4, 2012 8:38 PM, "Sharuzzaman Ahmat Raslan" <sharuzzaman(a)gmail.com> wrote: > Hi, > > The page: > http://directory.fedoraproject.org/wiki/Howto:MultiMasterReplication > > says that mmr.pl is not maintained. > > May I know what is the officially supported way to configure multi master > replication? > > Is there any guide in the wiki for the official way? > > Thanks. > > > -- > Sharuzzaman Ahmat Raslan > > -- > 389 users mailing list > 389-users(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/389-users >

2 1

official supported way for multi master replication
by Sharuzzaman Ahmat Raslan 05 Dec '12

05 Dec '12

Hi, The page: http://directory.fedoraproject.org/wiki/Howto:MultiMasterReplication says that mmr.pl is not maintained. May I know what is the officially supported way to configure multi master replication? Is there any guide in the wiki for the official way? Thanks. -- Sharuzzaman Ahmat Raslan

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users December 2012