Re: [ClusterLabs] two node cluster: vm starting - shutting down 15min later - starting again 15min later ... and so on

On 02/09/2017 10:48 AM, Lentes, Bernd wrote: > Hi, > > i have a two node cluster with a vm as a resource. Currently i'm just testing > and playing. My vm boots and shuts down again in 15min gaps. > Surely this is related to "PEngine Recheck Timer (I_PE_CALC) just popped > (90ms)" found in

Re: [ClusterLabs] Trouble setting up selfcompiled Apache in a pacemaker cluster on Oracle Linux 6.8

On 01/16/2017 10:16 AM, Souvignier, Daniel wrote: > Hi List, > > > > I’ve got trouble getting Apache to work in a Pacemaker cluster I set up > between two Oracle Linux 6.8 hosts. The cluster itself works just fine, > but Apache won’t come up. Thing is here, this Apache is different from a >

Re: [ClusterLabs] Problems with corosync and pacemaker with error scenarios

On 01/16/2017 11:18 AM, Gerhard Wiesinger wrote: > Hello Ken, > > thank you for the answers. > > On 16.01.2017 16:43, Ken Gaillot wrote: >> On 01/16/2017 08:56 AM, Gerhard Wiesinger wrote: >>> Hello, >>> >>> I'm new to corosync and pacemaker and I want to setup a nginx cluster >>> with quorum.

Re: [ClusterLabs] Pacemaker cluster not working after switching from 1.0 to 1.1

On 01/16/2017 01:16 PM, Rick Kint wrote: > >> Date: Mon, 16 Jan 2017 09:15:44 -0600 >> From: Ken Gaillot >> To: users@clusterlabs.org >> Subject: Re: [ClusterLabs] Pacemaker cluster not working after >> switching from 1.0 to 1.1 (resend as plain text) >> Message-ID:

Re: [ClusterLabs] Q (SLES11 SP4): Delay after node came up (info: throttle_send_command: New throttle mode: 0000 (was ffffffff))

On 01/16/2017 04:25 AM, Ulrich Windl wrote: > Hi! > > I have a question: The following happened in out 3-node cluster (n1, n2, n3): > n3 was DC, n2 was offlined, n2 came online again, n1 rebooted (went > offline/online), then n2 reboted (offline /online) > > I observed a significant delay after

Re: [ClusterLabs] [Question] About a change of crm_failcount.

On Thu, 09 Feb 2017 18:04:41 +0100 wf...@niif.hu (Ferenc Wágner) wrote: > Jehan-Guillaume de Rorthais writes: > > > PAF use private attribute to give informations between actions. We > > detect the failure during the notify as well, but raise the error > > during the promotion

Re: [ClusterLabs] Antw: Re: [Question] About a change of crm_failcount.

Jehan-Guillaume de Rorthais writes: > PAF use private attribute to give informations between actions. We > detect the failure during the notify as well, but raise the error > during the promotion itself. See how I dealt with this in PAF: > >

[ClusterLabs] two node cluster: vm starting - shutting down 15min later - starting again 15min later ... and so on

Hi, i have a two node cluster with a vm as a resource. Currently i'm just testing and playing. My vm boots and shuts down again in 15min gaps. Surely this is related to "PEngine Recheck Timer (I_PE_CALC) just popped (90ms)" found in the logs. I googled, and it is said that this is due to

Re: [ClusterLabs] Failed reload

On 02/09/2017 05:08 PM, Ken Gaillot wrote: > On 02/08/2017 02:15 AM, Ferenc Wágner wrote: >> Hi, >> >> There was an interesting discussion on this list about "Doing reload >> right" last July (which I still haven't digested entirely). Now I've >> got a related question about the current and

Re: [ClusterLabs] Failed reload

On 02/08/2017 02:15 AM, Ferenc Wágner wrote: > Hi, > > There was an interesting discussion on this list about "Doing reload > right" last July (which I still haven't digested entirely). Now I've > got a related question about the current and intented behavior: what > happens if a reload

Re: [ClusterLabs] Using "mandatory" startup order but avoiding depending clones from restart after member of parent clone fails

Delighful, thanks so much ken. On Thu, Feb 9, 2017 at 12:49 PM, Ken Gaillot wrote: > On 02/09/2017 08:50 AM, Alejandro Comisario wrote: > > Ken, thanks for yor reply. > > > > Since in our setup, we use active/active mysql clone, so i think that > > order is the only way to

Re: [ClusterLabs] Using "mandatory" startup order but avoiding depending clones from restart after member of parent clone fails

On 02/09/2017 08:50 AM, Alejandro Comisario wrote: > Ken, thanks for yor reply. > > Since in our setup, we use active/active mysql clone, so i think that > order is the only way to ensure what i want. > So, simple question, making order "Advisory", and tiking into > consideration that "maybe"

Re: [ClusterLabs] Antw: Re: [Question] About a change of crm_failcount.

On 02/09/2017 05:46 AM, Jehan-Guillaume de Rorthais wrote: > On Thu, 9 Feb 2017 19:24:22 +0900 (JST) > renayama19661...@ybb.ne.jp wrote: > >> Hi Ken, >> >> >>> 1. Return a "hard" error such as OCF_ERR_ARGS or OCF_ERR_PERM. When >>> Pacemaker gets one of these errors from an agent, it will ban the

Re: [ClusterLabs] Using "mandatory" startup order but avoiding depending clones from restart after member of parent clone fails

Ken, thanks for yor reply. Since in our setup, we use active/active mysql clone, so i think that order is the only way to ensure what i want. So, simple question, making order "Advisory", and tiking into consideration that "maybe" keystone starts before mysql, making it fail because of database