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 linethen, 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@xxxxxxxxxx> wrote:Mike Jackson wrote:jamsda wrote:Ok, so I'm guessing this is what happens behindthescenes (remove/re-create) when I do an"initializeconsumer" from the GUI right?It is, for all intents and purposes, thefunctional equivalent. Not exactly. Do perform a replica init, all youneed 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 -ssub -b cn=config '(objectclass=nsds5ReplicationAgreement)' cnThen 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: startThat starts the replica refresh (init).Step 3 - view repl init status with ldapsearch -remember to escape or quote the quotes in the repl agreement DNldapsearch -D "cn=directory manager" -w password -sbase -b "dn of your repl agreement" "objectclass=*" nsds5BeginReplicaRefresh nsds5replicaUpdateInProgress nsds5ReplicaLastInitStart nsds5ReplicaLastInitEnd nsds5ReplicaLastInitStatusThe init is complete when thensds5BeginReplicaRefresh 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 thesupplier and consumer.-- mike -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxxhttps://www.redhat.com/mailman/listinfo/fedora-directory-users--Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxxhttps://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@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users