[389-users] Problems with replication

[Rich Megginson]

On 10/15/2013 04:40 AM, Parasit Hendersson wrote:
> Hi,
> Once again we have a problem on our servers , this time with replication.
> In the log file repeatedly appear the same entries.
>
> [15/Oct/2013:11:08:43 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Beginning linger on the connection
> [15/Oct/2013:11:08:43 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): State: sending_updates -> 
> start_backoff
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): State: start_backoff -> backoff
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Cancelling linger on the connection
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Replica was successfully acquired.
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): State: backoff -> sending_updates
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Replica has a different generation 
> ID than the local data.
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Successfully released consumer
> [15/Oct/2013:11:08:47 +0200] NSMMReplicationPlugin - agmt="master port 
> 389 to slave port 389" (slave:389): Beginning linger on the connection
>
> I found in the archives and documentation similar problems , but they 
> all boiled down to the fact that replica isn't initialized.

Which is correct.

> A given solution in this case it does not help, i made (again) 
> initialization and the effect is exactly the same. What else can be 
> wrong?

You initialized the server "slave port 389" from the server "master port 
389" and you still get "Replica has a different generation ID"?

> Usually all changes from master are properly replicated, with some 
> unexplained exceptions and i don't know why.

If you are getting "Replica has a different generation ID" then nothing 
should be replicating from "master port 389" to "slave port 389".

>
> P. S. The same problem exists in all our slaves nodes.
>
> We use RHEL 6.4 with 389-ds-base-1.2.11.15-11.el6.x86_64
>
> With Regards
> Parasit Hendersson
> -- 
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users