sync agreement problem

[Vesa Alho]

Hi,

I'm having a problem with creating a sync agreement between two 
identical 389ds installations (1.2.11.5). I'm a bit puzzled since I've 
done this successfully before many times.

* Replication IDs are unique
* Both are Multiple Masters
* Both have same dc=domain,dc=com
* Schemas are identical
==> one difference from earlier setups is that SERVER1 and SERVER2 are 
in different domains, but 389s base suffix is still identical

Any ideas?

SERVER1 (sync agreement here)
[10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): State: start -> ready_to_acquire_replica
[10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): Trying secure slapi_ldap_init_ext
[10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): binddn = cn=Directory Manager
[10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): No linger to cancel on the connection
[10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): Unable to acquire replica: there is no replicated area 
"dc=domain,dc=com" on the consumer server. Replication is aborting.
[10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): Beginning linger on the connection
[10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): State: ready_to_acquire_replica -> stop_fatal_error
[10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): Incremental update failed and requires administrator action
[10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync" 
(ldap1:636): State: stop_fatal_error -> stop_fatal_error

SERVER 2
[10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 
Acquired consumer connection extension
[10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 
repl="dc=domain,dc=com": Begin incremental protocol
[10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 
replica="unknown": Unable to acquire replica: error: no such replica
[10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 
repl="dc=domain,dc=com": StartNSDS90ReplicationRequest: response=6 rc=0
[10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 
Relinquishing consumer connection extension

-Mr. Vesa Alho

[Grzegorz Dwornicki]

Maybe they need reinitialization. This error sugests this. I don't Know why
this is but had you tried this?
10 kwi 2013 12:52, "Vesa Alho"  napisał(a):
> Hi,
>
> I'm having a problem with creating a sync agreement between two identical
> 389ds installations (1.2.11.5). I'm a bit puzzled since I've done this
> successfully before many times.
> Replication IDs are unique
> Both are Multiple Masters
> Both have same dc=domain,dc=com
> Schemas are identical
>
> ==> one difference from earlier setups is that SERVER1 and SERVER2 are in
> different domains, but 389s base suffix is still identical
>
> Any ideas?
>
> SERVER1 (sync agreement here)
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: start -> ready_to_acquire_replica
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Trying secure slapi_ldap_init_ext
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): binddn = cn=Directory Manager
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): No linger to cancel on the connection
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Unable to acquire replica: there is no replicated area
> "dc=domain,dc=com" on the consumer server. Replication is aborting.
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Beginning linger on the connection
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: ready_to_acquire_replica -> stop_fatal_error
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Incremental update failed and requires administrator action
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: stop_fatal_error -> stop_fatal_error
>
> SERVER 2
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3 Acquired
> consumer connection extension
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> repl="dc=domain,dc=com": Begin incremental protocol
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> replica="unknown": Unable to acquire replica: error: no such replica
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> repl="dc=domain,dc=com": StartNSDS90ReplicationRequest: response=6 rc=0
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> Relinquishing consumer connection extension
> -Mr. Vesa Alho
>
> 389 users mailing list
> [e-mail].**org 
> https://admin.fedoraproject.**org/mailman/listinfo/389-usershttps://admin.fedoraproject.org/mailman/listinfo/389-users

[Vesa Alho]

Hmm, some problems with replication settings. Seems to work if I change 
other end to Consumer...I can manage with that. So my problem is solved.

-Vesa

On 04/10/2013 01:58 PM, Grzegorz Dwornicki wrote:
> Maybe they need reinitialization. This error sugests this. I don't Know
> why this is but had you tried this?
>
> 10 kwi 2013 12:52, "Vesa Alho" <[e-mail] >
> napisał(a):
> Hi,
>
> I'm having a problem with creating a sync agreement between two
> identical 389ds installations (1.2.11.5). I'm a bit puzzled since
> I've done this successfully before many times.
>
> * Replication IDs are unique
> * Both are Multiple Masters
> * Both have same dc=domain,dc=com
> * Schemas are identical
> ==> one difference from earlier setups is that SERVER1 and SERVER2
> are in different domains, but 389s base suffix is still identical
>
> Any ideas?
>
> SERVER1 (sync agreement here)
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: start -> ready_to_acquire_replica
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Trying secure slapi_ldap_init_ext
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): binddn = cn=Directory Manager
> [10/Apr/2013:13:21:25 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): No linger to cancel on the connection
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Unable to acquire replica: there is no replicated area
> "dc=domain,dc=com" on the consumer server. Replication is aborting.
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Beginning linger on the connection
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: ready_to_acquire_replica -> stop_fatal_error
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): Incremental update failed and requires administrator action
> [10/Apr/2013:13:21:26 +0300] NSMMReplicationPlugin - agmt="cn=sync"
> (ldap1:636): State: stop_fatal_error -> stop_fatal_error
>
> SERVER 2
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> Acquired consumer connection extension
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> repl="dc=domain,dc=com": Begin incremental protocol
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> replica="unknown": Unable to acquire replica: error: no such replica
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> repl="dc=domain,dc=com": StartNSDS90ReplicationRequest: response=6 rc=0
> [10/Apr/2013:10:21:27 +0000] NSMMReplicationPlugin - conn=90 op=3
> Relinquishing consumer connection extension
>
> -Mr. Vesa Alho
> --
> 389 users mailing list
> [e-mail].__org
> <mailto:[e-mail]>
> https://admin.fedoraproject.__org/mailman/listinfo/389-users
> <https://admin.fedoraproject.org/mailman/listinfo/389-users>
>
>
>
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users