[389-users] replicate_now script help
Ludwig Krispenz
lkrispen at redhat.com
Thu Nov 13 16:27:10 UTC 2014
ok, so there are two questions
- why doesn't the script work
- is th escript necesseray
To see why the script isn't working, could you provide the full script
and commandline of your latest attempt
I think the doc is not fully correct. If a consumer is taken offline the
supplier can no longer reach it and will try in increasing intervals, up
to 5 mins, but in my understanding it should retry every 5 mins. If the
cinsumer comes online the supplier does not know about this, and so it
could be up to 5 mins until the next retry. If you really want immediate
respons from the supplier the the suplier has to be notified eg by this
script.
But if the consumer has been offline for some time it could probaly be
acceptable to wait the 5 extra mins
Ludwig
On 11/13/2014 05:09 PM, ghiureai wrote:
>
>
>
> As per RHES doc:
> https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Forcing_Replication_Updates.html#Forcing_Replication_Updates-Forcing_Replication_Updates_from_the_Command_Line
>
> "Even if the replication agreements are configured to keep the
> supplier and consumer servers always in sync, it is not sufficient to
> bring back up-to-date a server that has been offline for over five
> minutes. The *Always Keep in Sync* option means that the server
> generates a replication operation for every update operation it
> processes. However, if this replication operation cannot be performed
> because the consumer is offline, the operation times out after 10
> minutes.
> 11.15.2. Forcing Replication Updates from the Command Line
> From the consumer that requires updating, run a script that prompts
> the supplier to send replication updates immediately. This script is
> shown in Example 11.5, “replicate_now Script Example”
> <https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Forcing_Replication_Updates.html#ex.Replicate_Now_Script_Example>.
>
> Copy this example script and name it something like
> |replicate_now.sh|. Substitute the actual values for the variables
> listed in Example 11.5, “replicate_now Script Example”
> <https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Forcing_Replication_Updates.html#ex.Replicate_Now_Script_Example>.
>
>
> *NOTE*
>
> This script must be run manually since it cannot be configured to run
> automatically as soon as the server, which was offline, comes back
> online again."''
>
>
>
>
>
> On 11/12/2014 09:54 AM, ghiureai wrote:
>> Hi LIst,
>> I'm new to 389-ds admin , I have cfg a multimaster replication
>> system , and read the RHES -DS documentation find the replicate_now
>> script which is suppose to trigger master rep updates < 10 min, the
>> script fails , there is no option for -1 in ldapsearch ...etc
>> Wodner if any of you have an update script , I 'm running 389-ds on
>> CentoS 6.5 .
>>
>> Thank you
>> Isabella
>>
>
>
>
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20141113/26c88cbe/attachment.html>
More information about the 389-users
mailing list