Hi, Alexander!
Thank for your reply

I was read your link, but it not related my issue. I will start new thread,
couse replica problem is resloved.


2016-09-01 11:10 GMT+03:00 Alexander Bokovoy <aboko...@redhat.com>:

> On Thu, 01 Sep 2016, Andrey Rogovsky wrote:
>
>> Hi, Alexander!
>>
>> Than you very much for help. Now I able to start replica, but have one
>> issue - schemes is not replicated:
>>
>> [01/Sep/2016:07:04:53 +0000] NSMMReplicationPlugin - Warning: unable to
>> replicate schema to host ldap2, port 389. Continuing with total update
>> session.
>> [01/Sep/2016:07:04:53 +0000] NSMMReplicationPlugin - Beginning total
>> update
>> of replica "agmt="cn=ExampleAgreement" (ldap2:389)".
>> [01/Sep/2016:07:04:53 +0000] NSMMReplicationPlugin - Need to create
>> replication keep alive entry <cn=repl keep alive 7,dc=example,dc=com>
>> [01/Sep/2016:07:04:53 +0000] NSMMReplicationPlugin - add dn: cn=repl keep
>> alive 7,dc=example,dc=com
>> objectclass: top
>> objectclass: ldapsubentry
>> objectclass: extensibleObject
>> cn: repl keep alive 7
>> [01/Sep/2016:07:04:58 +0000] NSMMReplicationPlugin - Finished total update
>> of replica "agmt="cn=ExampleAgreement" (ldap2:389)". Sent 415 entries.
>>
>> Can you help me with schemes?
>>
> I'm afraid I cannot help with that. You need to read RHDS documentation
> and design your own mechanism to make schema compatible on both sides.
> Replicating schema between IPA and plain RHDS is not really supported as
> nobody did that before, so you are on your own research and exploration
> path to see what configuration should be.
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Direct
> ory_Server/10/html/Deployment_Guide/Designing_the_
> Replication_Process-Using_Replication_with_Other_DS_Features
> .html#Using_Replication_with_Other_DS_Features-Schema_Replication
>
> --
> / Alexander Bokovoy
>
-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to