Problem with Repliation on 5.2 directory servers
796344May 26 2009 — edited Jan 7 2010Hello All,
I have a couple 5.2 directory servers setup in my test lab that I use to test out Security patches and such. Last Friday I installed some security patches and I noticed today that the replication quit working between the two ldap servers. I get the following errors: ( I have changed the server name to server1.domain)
[26/May/2009:13:38:51 -0600] - ERROR<8318> - Repl. Transport - conn=-1 op=-1 msgId=-1 - [S] Bind failed with response: Failed to bind to remote (900).
[26/May/2009:13:38:51 -0600] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Replication bind to consumer server1.domain:389 failed: Exceed password retry limit. Please try later.
[26/May/2009:13:38:51 -0600] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Failed to connect to replication consumer server1.domain:389
[26/May/2009:13:38:51 -0600] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Replication bind to consumer server1.idomain:389 failed: Exceed password retry limit. Please try later.
[26/May/2009:13:38:51 -0600] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Failed to connect to replication consumer server.domain:389
The replication has been working for years since I set it up, and this is the first problem that I have had with it. On server1 I can restart the instances and they startup, but I can not bind to it as directory manager or admin.
The only only thing that I can think of that happened a couple weeks before was that a coworker put in some schema changes for samba on server2 but not on server1. I had a word with him and removed the schema files and everything was fine until I rebooted the machine after the security patches. Could the inconsistent schemas corrupt something?
Thanks for any help,
Gary