LDAP Replication setup?

I have been following instructions to set up Single-Master Replication.

My problem arises when I attempt to create a replicaton agreement between the two servers after I provide the source and destination details I get an error:

Consumer server unreachable or invalid credentials supplied. Unable to perform subtree duplicaton verification.

I have double checked the user and password credientials and I get responses when I attempt to ping the replica server.

If anyone could give me some pointers on what I am doing wrong it would be much appreciated!

Message was edited by:

ksarah

[629 byte] By [ksaraha] at [2007-11-27 0:58:31]
# 1

With the little details that you specify here, there only pointer I can give is "Directory Server Administration Manual, Chapter 9 Replication" :-)

Are you using the console, or not ?

Have you enabled replication on the Consumer (read-only) and specified a user and password for the "Replication Manager" ?

Is this the same user you're referencing in the Replication Agreement ?

Have you checked the error logs on both the Master and the Consumer ?

Regards,

Ludovic.

ludovicpa at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

I am using the console.

These are the steps I have followed:

On server B:

Install iPlanet directory server.

Create root node with the same name as the root node that needs to be replicated from server A

Create a new user for replication. The supplier will provide these credentials to update the consumer:

Open directory console and select Directory tab > Config.

Right-click and select New > Other.

Select Person, and click OK.

In the new window, select the option Show Attribute Names.

In the values for cn and sn, enter cn=Replication Manager, cn=config.

Click Add Attribute and select userpassword from the list. Click OK.

Enter a password for the attribute userpassword.

Click Naming Attribute: sn Change. Clear sn and select cn. Click OK.

Click OK to create the user.

Set up the tree for replication.

Select the Configuration tab and expand it. Select the root node to replicate. On the right side:

Select Enable Replica.

In the Replicate Role, select Dedicated Consumer.

Under Common Settings, specify a purge delay of 1 week.

In the field, enter a new supplier DN, enter the cn=Replication Manager, cn=Config and click Add.

Click Save.

On server A:

Select the Configuration tab in the directory console and highlight the Replication node.

In the right pane:

Select the Enable Changelog checkbox.

Click Default.

Set Max Changelog age to 8 weeks.

Click Save to enable replication on this server.

In the Replication tree, highlight the tree to replicate.

Select the Enable Replica checkbox.

Select the Single Master radio button.

Under Common Settings, specify a replica id that is not currently in use by any other server. This has to be unique.

Specify a Purge Delay of 7 days.

Click Save to save replication settings for this database.

Create a replication agreement between server Aand server B. server A will push out data to server Band needs to provide appropriate credentials to EVRPRDEMPS2.

Right-click the database to replicate in the Replication tree. Select New Replication Agreement?

Enter a name for this agreement,

Enter a description

Click Next.

Click Other and in the new window, enter the fully qualified name of Server B. Enter the port number梩his should be 389 unless you have configured your Server B directory server to listen on another port.

In the Connection Information section, enter the user cn=Replication Manager, cn=Config in Bind as and the associated password in Password. Click Next. If Server A is able to bind successfully to Server B, the screen will go to the next step. If there is an error, make sure the information is correct and that server B is configured and running.

This is as far as I got before getting the error message mentioned in the original post

Am I missing something?

Message was edited by:

ksarah

ksaraha at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3

Looks good to me.

The error message indicates either incorrect host name (not resolved from Machine A to Machine B) or an invalid user/credentials.

Please check on Machine B, Access logs to see if there is a connection from machine A, and a Bind request.

If there is a Bind, check the DN received by server B, and the Bind result...

Ludovic.

ludovicpa at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 4

Machine B access log looks like:

[16/Apr/2007:14:22:47 +0100] conn=22 fd=1204 slot=1204 connection from 10.0.2.11 to 10.0.2.147

[16/Apr/2007:14:22:47 +0100] conn=22 op=0 BIND dn="cn=Replication Manager, cn=config" method=128 version=3

[16/Apr/2007:14:22:47 +0100] conn=22 op=0 RESULT err=32 tag=97 nentries=0 etime=0

Does this help identify what my problem might be?

ksaraha at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 5

> Machine B access log looks like:

>

> [16/Apr/2007:14:22:47 +0100] conn=22 fd=1204

> slot=1204 connection from 10.0.2.11 to 10.0.2.147

> [16/Apr/2007:14:22:47 +0100] conn=22 op=0 BIND

> dn="cn=Replication Manager, cn=config" method=128

> version=3

> [16/Apr/2007:14:22:47 +0100] conn=22 op=0 RESULT

> err=32 tag=97 nentries=0 etime=0

>

> Does this help identify what my problem might be?

I would request you to recheck the replication agreement config done on suplier server. Specially the Replication bind DN value. The log on consumer says the replication bind DN dn="cn=Replication Manager, cn=config" does not exists. Also the DN that is logged in the logs is dn="cn=Replication Manager, cn=config" and by default its dn="cn=Replication Manager,cn=replication, cn=config".

Regards

Randip Malakar

Randip_Malakara at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 6
Thanks for the help guys,looks like it was the way the user name was built up by the cn and sn fields when creating the user. Have created a new user and replication is now working fine!
ksaraha at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 7
Hi Do you know how to setup single master replication using CLI on fedora directory serverPlease helpThanksDejo
Dejoa at 2007-7-11 23:32:30 > top of Java-index,Web & Directory Servers,Directory Servers...