[389-users] repl_set_mtn_referrals: could not set referrals for replica

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi again

What's the difference between the referrals specified in the suffixes
and the referrals specified in a replica? We have had ever the
referrals specified in the suffix. Do you mean to set them too in the
replica?

Regards.

(Testing 389DS 1.2.3, having problems with schema syntaxes...)


2009/10/19 Rich Megginson <rmeggins at redhat.com>:
> Juan Asensio S?nchez wrote:
>>
>> Hi
>>
>> We are having problems with replication. We have four master servers
>> replicating one database (database 1), and two other servers in other
>> building that are masters of other database (database 2). Replication
>> between the databases of the others are in hub mode (server1 of
>> building1 with server1 of building1, and server2 of building1 with
>> server2 of building2; server3 and server4 of building1 only have
>> agreements with server1 and server2 of building1). Yesterday we had to
>> remove the replica of server4 of database 1. Next, we did ree-enable
>> the replica and the replication agreements, but the replica was
>> enabled with a different id than before. Now, we have this error on
>> all servers, although replication is working fine:
>>
>> [16/Oct/2009:12:44:39 +0200] NSMMReplicationPlugin -
>> repl_set_mtn_referrals: could not set referrals for replica
>> dc=domain,dc=local: 1
>>
>
> I don't think this is a critical error. ?You can manually set the referrals
> to use - in the console for the Replica config, at the bottom of that window
> (under the Supplier DN area) you can specify the referrals to use. ?However,
> you will have to manage these manually - they are not set automatically like
> the regular replication referrals are.
>
>> (dc=domain,dc=local is the prefix that owns the database 1). I don't
>> know if this error is critical, but i don't like to see errors in the
>> log (call me fool if you want). I have read some posts:
>>
>> - http://blogs.sun.com/marcos/entry/on_cleanruv
>> - http://blogs.sun.com/piotr/entry/how_to_clean_ruv_s
>>
>> All about Sun, but i am not sure if this will work, or if it is
>> dangerous because it says that the solution is unsupported and
>> irreversible. How can I get rid of this message? is it critical?
>>
>
> You could try using that. ?I would suggest backing up all of your data and
> config first.
>>
>> Regards and thanks in advance.
>>
>> --
>> 389 users mailing list
>> 389-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>
>
>
> --
> 389 users mailing list
> 389-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux