Command-line Consumer Initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the response. So after step 1 here's my
output:

dn: cn="Replication to
host2.xyz.com",cn=replica,cn="dc=xyz,dc=com",cn=mapping
tree,cn=config
cn: "Replication to host2.xyz.com"
cn: Replication to host2.xyz.com

So how would step 2 look on the command-line? Here's
what I started with:

ldapmodify -D "cn=directory manager" -w password -b
n="Replication to
host2.xyz.com",cn=replica,cn="dc=xyz,dc=com",cn=mapping
tree,cn=config

but where do I specify the rest of these attributes:

changetype: modify
replace: nsds5BeginReplicaRefresh
nsds5BeginReplicaRefresh: start




Thanks,
Jim

--- Richard Megginson <rmeggins at redhat.com> wrote:

> Mike Jackson wrote:
> > jamsda wrote:
> >> Ok, so I'm guessing this is what happens behind
> the
> >> scenes (remove/re-create) when I do an
> "initialize
> >> consumer" from the GUI right?
> >
> > It is, for all intents and purposes, the
> functional equivalent.
> Not exactly.  Do perform a replica init, all you
> need is the DN of the 
> replication agreement.
> Step 1 - find the DN of the replication agreement
> with ldapsearch:
> ldapsearch -D "cn=directory manager" -w password -s
> sub -b cn=config 
> '(objectclass=nsds5ReplicationAgreement)' cn
> Then choose the repl agreement you are interested in
> 
> Step 2 - initiate repl init using ldapmodify
> ldapmodify -D "cn=directory manager" -w password
> dn: dn of your repl agreement from step 1
> changetype: modify
> replace: nsds5BeginReplicaRefresh
> nsds5BeginReplicaRefresh: start
> 
> That starts the replica refresh (init). 
> 
> Step 3 - view repl init status with ldapsearch -
> remember to escape or 
> quote the quotes in the repl agreement DN
> ldapsearch -D "cn=directory manager" -w password -s
> base -b "dn of your 
> repl agreement" "objectclass=*"
> nsds5BeginReplicaRefresh 
> nsds5replicaUpdateInProgress
> nsds5ReplicaLastInitStart 
> nsds5ReplicaLastInitEnd nsds5ReplicaLastInitStatus
> 
> The init is complete when the
> nsds5BeginReplicaRefresh attribute is 
> absent.  Then you can check the status with
> nsds5ReplicaLastInitStatus, 
> which should contain the string "Total update
> succeeded" if successful.  
> If there are errors, check the error logs on the
> supplier and consumer.
> >
> > -- 
> > mike
> >
> > -- 
> > Fedora-directory-users mailing list
> > Fedora-directory-users at redhat.com
> >
>
https://www.redhat.com/mailman/listinfo/fedora-directory-users
> > --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-directory-users
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux