help needed regarding replication in ds5.2sp4
Hi ,
I am new to ldap . I am able to establish replication between master and consumer and trying to update it is getting update but i am geting the following error
in error log
INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Replication bind to consumer alpha.ad.com:19941 failed:
[16/May/2007:13:48:26 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Failed to connect to replication consumer alpha.ad.com:19941
[16/May/2007:13:48:26 -0700] - ERROR<8318> - Repl. Transport - conn=-1 op=-1 msgId=-1 - [S] Bind failed with response: Failed to bind to remote (900).
Please help me regarding this .
Message was edited by:
ap7926
[727 byte] By [
ap7926a] at [2007-11-27 4:35:30]
# 1
As the error says it can't bind (login) to LDAP on the consumer, apparently because it can't connect to "consumer.alpha.ad.com" on port 19941.
(1) Is that really the port you sent the Directory Server on consumer.alpha.ad.com to listen to (the value of nsslapd-port)?
(2) Is nsslapd running on consumer?
(3) Does a "netstat -an | grep 19941" on consumer show anything in LISTEN state?
(4) Can you manually connect to it via:
(A) Other LDAP tools like "ldapsearch -h consumer.alpha.ad.com -p 19941 ..."
(B) "telnet consumer.alpha.ad.com 19941" (just to see if it connects, don't expect to get any useful interaction).
(C) Try both A & B from consumer locally and then remotely from the supplier.
If any of the above fail it's likely that you're using a different port (likely the default of 389), or that the directory server isn't running on consumer. If telnet works from consumer but not from supplier then check for firewalls.
If all of that works then the next series of steps is to see if you can bind manually to the replication manager using different tools (like ldapsearch).
# 2
Thank you for the reply.
here i m able to replicate and update the data from master replica to consumer .Here master and consumer are instances of same server.
Please clarify my doubt
if we cant bind how come data is replicated and getting update .
Message was edited by:
ap7926
# 3
If data is getting replicated from master to consumer then the bind for that specific replication agreement is working.
Check your timestamps and current log entries. Are the "Failed to connect to replication" messages currently being generated? As long as your replication agreement is enabled the supplier will try to keep things up and running, retrying a failed consumer regularly (and generating about 1 set of log messaages per minute on my systems). So you'll get those messages on the supplier when a good consumer is down (the nsslapd directory server process that is).
If you don't have these messages being generated currently then this probably means that your consumer was down around "16/May/2007:13:48:26 -0700" but is ok now. In that case those messages aren't of big concern. They're just telling you that you had a problem, which you hopefully already knew about.
If replication is working (test by making a change on the supplier and checking it on the consumer) AND you're still concurrently getting these messages regularly then you have something interesting going on, probably due to a configuration issue. Without seeing the details it's difficult say what it would be.
# 4
it is working fine now.Its a blunder mistake I did.
I gave a directory manager password instead of giving the Consumer's replication manager one while creating a RA to send updates to Consumer.
Everything works fine after I gave the Consumer's Rep Manger password in order to bind from Master to consumer.
still i wonder how does replication work with directory manger password without adding in Bind dn.
Thanks
Message was edited by:
ap7926
