[ClusterLabs] Antw: Re: Antw: Re: Antw: Re: Antw: pacemaker doesn't correctly handle a resource after time/date change

Thu Jul 30 07:51:00 EDT 2015

Does the bug have to be reported somewhere else besides this mail thread?

Thank you,
Kostya

On Wed, Jul 29, 2015 at 4:51 PM, Vijay Partha <vijaysarathy94 at gmail.com>
wrote:

> Thanks for the reply ulrich.
>
> I do have these 2 files but will pacemaker automatically restart all the
> instance by itself if the apache server has gone down.Do i need to change
> any of my scripts? I want to make sure that a single command to start an
> apache service in one node should also start the apache servers running on
> other nodes.
>
> On Wed, Jul 29, 2015 at 7:12 PM, Kostiantyn Ponomarenko <
> konstantin.ponomarenko at gmail.com> wrote:
>
>> Guys, it is not "that" thread for the last two messages =)
>>
>> Thank you,
>> Kostya
>>
>> On Wed, Jul 29, 2015 at 4:34 PM, Ulrich Windl <
>> Ulrich.Windl at rz.uni-regensburg.de> wrote:
>>
>>> >>> Vijay Partha <vijaysarathy94 at gmail.com> schrieb am 29.07.2015 um
>>> 14:51 in
>>> Nachricht
>>> <CAMmMq+btg3rwnPH2xOLS3v9WG3i9pDj45tgPcYpKzHGdNdCXPg at mail.gmail.com>:
>>> > Hi.
>>> >
>>> > Victor, Whatever you said i had tried and got it working. Thank you.
>>> >
>>> > Could you guys answer the following questions please?
>>> >
>>> > 1.) I have 2 apache services running on the same node. If the services
>>> go
>>> > down can pacemaker restart it?
>>> > 2.) I have 2 apache services running on different nodes. Can i control
>>> both
>>> > the resources from a single node by making use of pacemaker?
>>>
>>> The answer is rather simple: If you have a sript to start/stop/check on
>>> of your apache instances, pamemaker will be able to take care of your
>>> instances.
>>>
>>> In SLES11SP3 I only found those:
>>> # find /usr/lib/ocf/ -iname apa\*
>>> /usr/lib/ocf/lib/heartbeat/apache-conf.sh
>>> /usr/lib/ocf/resource.d/heartbeat/apache
>>>
>>> Regards,
>>> Ulrich
>>>
>>> >
>>> > On Wed, Jul 29, 2015 at 6:14 PM, Kostiantyn Ponomarenko <
>>> > konstantin.ponomarenko at gmail.com> wrote:
>>> >
>>> >> So, is it considered as a bug in Pacemaker?
>>> >> Buy the way, while the "failure-timeout" is set to 1 hour and with the
>>> >> "cluster-recheck-interval" of 15 min, the resource is started by the
>>> >> cluster sometime after 1 hour and 15 min time period.
>>> >>
>>> >> Thank you,
>>> >> Kostya
>>> >>
>>> >> On Mon, Jul 27, 2015 at 9:09 AM, Ulrich Windl <
>>> >> Ulrich.Windl at rz.uni-regensburg.de> wrote:
>>> >>
>>> >>> >>> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com>
>>> schrieb am
>>> >>> 24.07.2015
>>> >>> um 16:53 in Nachricht
>>> >>> <CAEnTH0fPx9Zjj71gW92xordkOw1kk7kbT8xtO7M1En9w5MCyVw at mail.gmail.com
>>> >:
>>> >>> > On Fri, Jul 24, 2015 at 1:21 PM, Ulrich Windl <
>>> >>> > Ulrich.Windl at rz.uni-regensburg.de> wrote:
>>> >>> >
>>> >>> >> 25 years backwards?
>>> >>> >
>>> >>> >
>>> >>> > I've tried to set time back for:
>>> >>> >     2 hours;
>>> >>> >     10 min.
>>> >>> > The result was the same as with:
>>> >>> >     # date --set="1990-01-01 01:00:00"
>>> >>> >
>>> >>> > Setting time to 5 min back doesn't lead to that issue - the
>>> resource is
>>> >>> > restarted.
>>> >>> > There is no such problem with setting time forward.
>>> >>>
>>> >>> I'm afraid no programmer ever took provisions for time running
>>> backwards.
>>> >>> It may be as simple as that. Recently thres has been even heavy
>>> discussion
>>> >>> (elsewhere) about the bad effects of inserting a leap second,
>>> realizing
>>> >>> that the POSIX interface has to means of detecting a leap second...
>>> >>>
>>> >>> >
>>> >>> > P.S.:The resource has it's monitor interval set to 30 sec.
>>> >>> >
>>> >>> > Thank you,
>>> >>> > Kostya
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> _______________________________________________
>>> >>> Users mailing list: Users at clusterlabs.org
>>> >>> http://clusterlabs.org/mailman/listinfo/users
>>> >>>
>>> >>> Project Home: http://www.clusterlabs.org
>>> >>> Getting started:
>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> >>> Bugs: http://bugs.clusterlabs.org
>>> >>>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Users mailing list: Users at clusterlabs.org
>>> >> http://clusterlabs.org/mailman/listinfo/users
>>> >>
>>> >> Project Home: http://www.clusterlabs.org
>>> >> Getting started:
>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> >> Bugs: http://bugs.clusterlabs.org
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > With Regards
>>> > P.Vijay
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list: Users at clusterlabs.org
>>> http://clusterlabs.org/mailman/listinfo/users
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>>>
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>>
>
>
> --
> With Regards
> P.Vijay
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150730/da486a2a/attachment-0003.html>