Re: Re: A multi-master disaster

[Ulf Weltman <ulf.weltman@xxxxxx>]

Quotes are expected to be escaped in the access log.  I wonder if you have a space in the cn value of the mapping node, that is, something like cn="dc=edops, dc=com".  That would allow the import to succeed but the node would not be found without the space to set the referral.  Compare the mapping tree entries in the dse.ldif files on your two replicas.

Edward Capriolo wrote:

[07/Jul/2008:12:56:49 -0400] conn=2 op=167 SRCH base="cn=repl,
cn=replica, cn=\22dc=edops,dc=com\22, cn=mapping tree, cn=config"
scope=0 filter="(|(objectClass=*)(objectClass=ldapsubentry))"
attrs="nsds5replicaLastUpdateStart nsds5replicaLastUpdateEnd
nsds5replicaChangesSentSinceStartup nsds5replicaLastUpdateStatus
nsds5replicaUpdateInProgress nsds5replicaLastInitStart
nsds5replicaLastInitEnd nsds5replicaLastInitStatus
nsds5BeginReplicaRefresh"

To follow up. Are these entries being escaped for the log or is it
that the console tool is generating these incorrectly? I had similar
\22 trying to configure ACI from the gui.


On Mon, Jul 7, 2008 at 11:17 AM, Edward Capriolo <edlinuxguru@xxxxxxxxx> wrote:
  

Sorry for the funny title. I THINK* this may be a bug of multi-master
replication agreement created from the Windows Version of the Console
Tool but I was hoping someone could shed some light on this. I have
set up multi master replication before and did not run into this
issue.


I go about the normal process described in the documentation to setup
a multi-master replication agreement for only one suffix of my
directory server. dc_edops_dc_com.
Enable changelog
Select multi-master replication
Give each server a unique id

I initialize the side of the connection with data. (I also have tried
using ldif to get both sides in sync before the transfer. )

On the side I initialize from I get these messages in the error log.

[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Workers
finished; cleaning up...
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Workers cleaned up.
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Cleaning up
producer thread...
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Indexing
complete.  Post-processing...
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Flushing caches...
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Closing files...
[02/Jul/2008:18:25:19 -0400] - import dc_edops_dc_com: Import
complete.  Processed 42 entries in 2 seconds. (21.00 entries/sec)
[02/Jul/2008:18:25:19 -0400] NSMMReplicationPlugin -
multimaster_be_state_change: replica dc=edops,dc=com is coming online;
enabling replication
[02/Jul/2008:18:25:20 -0400] NSMMReplicationPlugin -
repl_set_mtn_referrals: could not set referrals for replica
dc=edops,dc=com : 32

At this point actually multi-master replication is enabled, but the B
side of the connection has some strange referral to the A side. When I
connect to side B of the replication it seems like there is one more
level there.

Does anyone understand why this simple setup would not be working?

    

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

  

<<attachment: smime.p7s>>

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users