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

2015-08-28 Thread Vladislav Bogdanov
28.08.2015 12:25, Kostiantyn Ponomarenko wrote: In my case the final solution will be shipped to different counties which means different time zones. Why not to keep all HW clocks in UTC? And the replacement of one of the nodes in the working solution could happens. So the possibilities of

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

2015-08-28 Thread Kostiantyn Ponomarenko
The issue doesn't hurt me right now as we use a workaround for that. But a workaround is not a fix of the problem. Thank you, Kostya On Fri, Aug 28, 2015 at 12:25 PM, Kostiantyn Ponomarenko konstantin.ponomare...@gmail.com wrote: In my case the final solution will be shipped to different

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

2015-08-21 Thread Kostiantyn Ponomarenko
I agree that the possibility of this to happen is really really small =) But the consequences can be huge =( Thank you, Kostya On Fri, Aug 21, 2015 at 4:06 PM, Kostiantyn Ponomarenko konstantin.ponomare...@gmail.com wrote: As I wrote in the previous email, it could happen when NTP servers are

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

2015-08-21 Thread Kostiantyn Ponomarenko
As I wrote in the previous email, it could happen when NTP servers are unreachable before Pacemaker's start, and then, after some time, NTP becomes reachable again. So it is possible that time will be synchronized in any direction: 15 min or 23 min or 1 hour or 12 hours backward/forward. And in

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

2015-08-16 Thread Andrew Beekhof
On 8 Aug 2015, at 12:43 am, Kostiantyn Ponomarenko konstantin.ponomare...@gmail.com wrote: Hi Andrew, So the issue is: Having one node up and running, set time on the node backward to, say, 15 min (generally more than 10 min), then do stop for a resource. That leads to the next -

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

2015-08-04 Thread Kostiantyn Ponomarenko
On Tue, Aug 4, 2015 at 3:57 AM, Andrew Beekhof and...@beekhof.net wrote: Github might be another. I am not able to open an issue/bug here https://github.com/ClusterLabs/pacemaker Thank you, Kostya ___ Users mailing list: Users@clusterlabs.org

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

2015-07-30 Thread Kostiantyn Ponomarenko
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 vijaysarath...@gmail.com wrote: Thanks for the reply ulrich. I do have these 2 files but will pacemaker automatically restart all the instance by itself

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

2015-07-29 Thread Ulrich Windl
Vijay Partha vijaysarath...@gmail.com schrieb am 29.07.2015 um 14:51 in Nachricht cammmq+btg3rwnph2xols3v9wg3i9pdj45tgpcypkzhgdndc...@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