jamsda wrote: > 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 > No, just ldapmodify -D "cn=directory manager" -w password Once you type this in, ldapmodify will wait for your input: dn: cn="Replication to host2.xyz.com",cn=replica,cn="dc=xyz,dc=com",cn=mapping tree,cn=config changetype: modify replace: nsds5BeginReplicaRefresh nsds5BeginReplicaRefresh: start ^^ is a blank line then, type Ctrl-D to end the input - you should get the usual shell command prompt again. > 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 > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3178 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20061026/1dae49f4/attachment.bin
