replication question

This seems to be pretty strange thing happening...we have a single master replication in which we have a master and two consumers.

I have loaded the data into the Master and setup all the RA's between the Master and two Consumers afterwhich Initialization of masters is dont..everything is woriking fine.

I was Testing the consumer for referrals and i observed that when i logged onto the Consumer replicat through the GUI with

"cn=Directory Manager",I am able to modify the entries on the Consumer. This is a pretty strange occurence as the Consumers should'nt be handling any Modifications..Any reason for this strange behaviour?Help would be greatly appreciatd

[691 byte] By [anandkaturia] at [2007-11-27 11:15:30]
# 1

If I understand this correctly, what is happening is the consumer is referring the change to your master ldap server. The master changes the data and then pushes the changes out to your consumer ldap servers.

You might want to read the section in the manual about referrals. It would probably explain things in more detail.

Gary

gpeck1a at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

Yep,

The Sun console follows replication referrals to the master pretty transparently, so that it appears that you're modifying data directly on the consumer.

If you're curious, try watching the logs on both the master and the consumer while you're 'modifying' data in the GUI on the consumer.

gtholberta at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3

So do you mean to say tht the behind the scene the entry is being created on Master and then replicated to Consumer?

Because i hve logged onto the consumer and when iam trying to add a user, iam getting successful..Does'nt the DS throw any exception tht mentions " can't modify as this is Consumer " or "being referred to Master" ...

I have even seen the access logs on Master and Consumer and they look as follows:

Master Access Logs:

conn=213889 op=-1 msgId=-1 - fd=40 slot=40 LDAP connection from 151.140.141.143 to 172.20.31.220

[23/Jul/2007:11:16:33 -0400] conn=213889 op=0 msgId=138 - BIND dn="cn=Directory Manager" method=128 version=3

[23/Jul/2007:11:16:33 -0400] conn=213889 op=0 msgId=138 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"

[23/Jul/2007:11:16:33 -0400] conn=213889 op=1 msgId=139 - ADD dn="uid=testuser1,dc=company,dc=com"

[23/Jul/2007:11:16:33 -0400] conn=213889 op=1 msgId=139 - RESULT err=0 tag=105 nentries=0 etime=0 csn=46a4c6510000000b0000

[23/Jul/2007:11:16:33 -0400] conn=213889 op=2 msgId=140 - UNBIND

Consumer Access Logs:

nn=829 op=1 msgId=2 - RESULT err=0 tag=101 nentries=1 etime=0

[23/Jul/2007:11:16:12 -0400] conn=829 op=2 msgId=3 - EXT oid="1.3.6.1.4.1.42.2.27.9.6.1"

[23/Jul/2007:11:16:12 -0400] conn=829 op=2 msgId=3 - RESULT err=0 tag=120 nentries=0 etime=0

[23/Jul/2007:11:16:12 -0400] conn=829 op=3 msgId=4 - EXT oid="1.3.6.1.4.1.42.2.27.9.6.6"

[23/Jul/2007:11:16:12 -0400] conn=829 op=3 msgId=4 - RESULT err=0 tag=120 nentries=0 etime=0

[23/Jul/2007:11:16:33 -0400] conn=828 op=59 msgId=136 - SRCH base="" scope=0 filter="(|(objectClass=*)(objectClass=ldapsubentry))" attrs=ALL

[23/Jul/2007:11:16:33 -0400] conn=828 op=59 msgId=136 - RESULT err=0 tag=101 nentries=1 etime=0

[23/Jul/2007:11:16:33 -0400] conn=828 op=60 msgId=137 - ADD dn="uid=testuser1,dc=company,dc=com"

[23/Jul/2007:11:16:33 -0400] conn=828 op=60 msgId=137 - RESULT err=10 tag=105 nentries=0 etime=0

[23/Jul/2007:11:16:33 -0400] conn=829 op=4 msgId=5 - EXT oid="1.3.6.1.4.1.42.2.27.9.6.1"

[23/Jul/2007:11:16:33 -0400] conn=829 op=4 msgId=5 - RESULT err=0 tag=120 nentries=0 etime=0

[23/Jul/2007:11:16:33 -0400] conn=829 op=5 msgId=6 - EXT oid="1.3.6.1.4.1.42.2.27.9.6.4"

[23/Jul/2007:11:16:33 -0400] conn=829 op=5 msgId=6 - RESULT err=0 tag=120 nentries=0 etime=0

[23/Jul/2007:11:16:33 -0400] conn=829 op=6 msgId=7 - EXT oid="1.3.6.1.4.1.42.2.27.9.6.8"

[23/Jul/2007:11:16:33 -0400] conn=829 op=0 msgId=7 - ADD dn="uid=testuser1,dc=company,dc=com"

[23/Jul/2007:11:16:33 -0400] conn=829 op=0 msgId=7 - RESULT err=0 tag=105 nentries=0 etime=0 csn=46a4c6510000000b0000

Is there any exact line in the Access logs of Consumer that specifies the Modify operation has been referred to the Master.. Because i have seen mamy entries in the Access logs of the Consumer( in which i tried to make the modifcation) with objectclass= referral...

And i dont see any of such kind of entries in the Access logs of other Consumer in the Setup...Does this indicate that the Consumer on which i was trying to make the modification has reffered to the Master and the actual add operation took place in the Operation.....?

The objectclass in the access logs of the consumer ar as follows:

conn=828 op=36 msgId=113 - SRCH base="dc=company,dc=com" scope=1 filter="(|(&(numSubordinates=*)(numSubordinate

s>=1)(|(objectClass=*)(objectClass=ldapsubentry)))(objectClass=referral)(obj ectClass=organization)(objectClass=organizationalUnit)(objectClass

=netscapeServer)(objectClass=netscapeResource)(objectClass=domain))" attrs="objectClass numSubordinates ref aci"

Also can anyone let me know what exactly the term "csn = no" means beside the in the access logs?

anandkaturia at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 4

> So do you mean to say tht the behind the scene the entry is being created

> on Master and then replicated to Consumer?

Yes, exactly.

> Is there any exact line in the Access logs of Consumer that specifies the

> Modify operation has been referred to the Master..

Yes:

[23/Jul/2007:11:16:33 -0400] conn=828 op=60 msgId=137 - ADD dn="uid=testuser1,dc=company,dc=com"

[23/Jul/2007:11:16:33 -0400] conn=828 op=60 msgId=137 - RESULT err=10 tag=105 nentries=0 etime=0

err=10 means a referral was recevied.

That's the last we see of conn=828 in the log snippet.

gtholberta at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 5

Thanks for the reply

anandkaturia at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 6

And to conclude with this thread, csn=xxxxxx is an additional information for tracking changes in a replicated environment.

Each change applied to a Master is identified with a unique Change Sequence Number (csn).

That CSN is used in the replication protocol to order changes and associate replication meta-data. When the change is replicated to a Consumer, the same CSN is also logged in access log and that allows to track and check that a change was replicated successfully.

Regards,

Ludovic.

ludovicpa at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...
# 7

Thanks fr the reply ludo

anandkaturia at 2007-7-29 14:13:16 > top of Java-index,Web & Directory Servers,Directory Servers...