Hi Ken,
I don't see any issues in the logs, periodically this is in the logs:
Jun 20 11:52:19 [5613] zfs-serv3 crmd: info: crm_timer_popped:
PEngine Recheck Timer (I_PE_CALC) just popped (90ms)
Jun 20 11:52:19 [5613] zfs-serv3 crmd: notice: do_state_transition:
Good Day,
We had a node failure and we had to rebuild the whole server from scratch.
After rebuilding Asterisk01 and rejoining it to the cluster something isn't
working 100%.
It does fail over but the corosync.log file on the second node is growing
at 1Gb every 15min.
I have attached a piece of t
On Wed, Jun 20, 2018 at 01:58:18PM +0200, Mark Prinsloo wrote:
> Good Day,
>
> We had a node failure and we had to rebuild the whole server from scratch.
> After rebuilding Asterisk01 and rejoining it to the cluster something isn't
> working 100%.
>
> It does fail over but the corosync.log file o
On Tue, Jun 19, 2018 at 1:47 PM Jason Gauthier wrote:
>
> On Tue, Jun 19, 2018 at 6:58 AM Christine Caulfield
> wrote:
> >
> > On 19/06/18 11:44, Jason Gauthier wrote:
> > > On Tue, Jun 19, 2018 at 3:25 AM Christine Caulfield
> > > wrote:
> > >>
> > >> On 19/06/18 02:46, Jason Gauthier wrote:
I tried testing out a fencing configuration that I had working with a 3-node
cluster, using a 2-node cluster. What I found is that when I power off one of
the nodes forcibly, it does not get fenced and rebooted as it does on a 3-node
cluster. I have verified that I can fence and reboot one nod
Make sure quorum is disabled. Quorum doesn't work on 2-node clusters.
Also be sure to set a fence delay on the "primary" node (however you
define that) so that you have some predictability about which node will
live in a comms break event.
digimer
On 2018-06-20 05:22 PM, Casey & Gina wrote:
> I t
On Wed, 20 Jun 2018 17:24:41 -0400
Digimer wrote:
> Make sure quorum is disabled. Quorum doesn't work on 2-node clusters.
It does with the "two_node" parameter enabled in corosync.conf...as far as I
understand it anyway...
___
Users mailing list: Users
My corosync.conf (which I don't manually create, I guess pcs does this?)
already has:
quorum {
provider: corosync_votequorum
two_node: 1
}
No go.
> On 2018-06-20, at 3:46 PM, Jehan-Guillaume de Rorthais
> wrote:
>
> On Wed, 20 Jun 2018 17:24:41 -0400
> Digimer wrote:
>
>> Make sure q
On 2018-06-20 05:46 PM, Jehan-Guillaume de Rorthais wrote:
> On Wed, 20 Jun 2018 17:24:41 -0400
> Digimer wrote:
>
>> Make sure quorum is disabled. Quorum doesn't work on 2-node clusters.
>
> It does with the "two_node" parameter enabled in corosync.conf...as far as I
> understand it anyway...
Note: Please reply to he list, not me directly.
The stonith delay helps predict who will win in a comms break event
where both try to fence the other at the same time. If you disable
quorum and it still doesn't fence, something else is wrong (and it's not
related to the delay).
Get the cluster he
Does this mean that fencing can't actually work in a 2-node cluster?? Or is it
just that the delay needs set differently on one of the hosts and it will start
working?
> On 2018-06-20, at 3:50 PM, Digimer wrote:
>
> On 2018-06-20 05:46 PM, Jehan-Guillaume de Rorthais wrote:
>> On Wed, 20 Jun
Fencing is required on all clusters, and specially on 2-node ones.
https://www.alteeve.com/w/The_2-Node_Myth
digimer
On 2018-06-20 05:53 PM, Casey & Gina wrote:
> Does this mean that fencing can't actually work in a 2-node cluster?? Or is
> it just that the delay needs set differently on one o
> Note: Please reply to he list, not me directly.
I intended to. I don't know why sometimes when I click "Reply" it defaults to
the list but sometimes it does not. Anyways...
> The stonith delay helps predict who will win in a comms break event
> where both try to fence the other at the same t
> On 2018-06-20, at 3:59 PM, Casey & Gina wrote:
>
>> Get the cluster healthy, tail the system logs from both nodes, trigger a
>> fault and wait for things to settle. Then share the logs please.
>
> What do you mean by "system logs"? Do you mean the corosync.log? Triggering
> a fault is power
Please forgive me, I had inadvertently had stonith-enabled=false when I thought
I had it true. The fencing/rebooting is now working. However, in light of
what you brought up earlier, how do I set a delay preference different for one
of the two hosts in case of a communications failure?
> On 2
Silly question; Did you actually enable stonith? Can you share your config?
digimer
On 2018-06-20 06:04 PM, Casey & Gina wrote:
>> On 2018-06-20, at 3:59 PM, Casey & Gina wrote:
>>
>>> Get the cluster healthy, tail the system logs from both nodes, trigger a
>>> fault and wait for things to settl
On Wed, 2018-06-20 at 13:30 +0200, Stefan Krueger wrote:
> Hi Ken,
>
> I don't see any issues in the logs, periodically this is in the logs:
>
> Jun 20 11:52:19 [5613] zfs-serv3 crmd: info:
> crm_timer_popped:PEngine Recheck Timer (I_PE_CALC) just
> popped (90ms)
> Jun 20 11
Source code for the first (and likely only) release candidate for
Pacemaker version 1.1.19 is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.19-rc1
The 1.1 series is no longer actively maintained. This is a maintenance
release to wrap up selected changes backpor
21.06.2018 00:50, Digimer пишет:
> On 2018-06-20 05:46 PM, Jehan-Guillaume de Rorthais wrote:
>> On Wed, 20 Jun 2018 17:24:41 -0400
>> Digimer wrote:
>>
>>> Make sure quorum is disabled. Quorum doesn't work on 2-node clusters.
>>
>> It does with the "two_node" parameter enabled in corosync.conf...
21.06.2018 01:12, Casey & Gina пишет:
> Please forgive me, I had inadvertently had stonith-enabled=false when
> I thought I had it true. The fencing/rebooting is now working.
> However, in light of what you brought up earlier, how do I set a
> delay preference different for one of the two hosts in
On 06/21/2018 05:52 AM, Andrei Borzenkov wrote:
> 21.06.2018 00:50, Digimer пишет:
>> On 2018-06-20 05:46 PM, Jehan-Guillaume de Rorthais wrote:
>>> On Wed, 20 Jun 2018 17:24:41 -0400
>>> Digimer wrote:
>>>
Make sure quorum is disabled. Quorum doesn't work on 2-node clusters.
>>> It does with
On 06/21/2018 06:02 AM, Andrei Borzenkov wrote:
> 21.06.2018 01:12, Casey & Gina пишет:
>> Please forgive me, I had inadvertently had stonith-enabled=false when
>> I thought I had it true. The fencing/rebooting is now working.
>> However, in light of what you brought up earlier, how do I set a
>>
On Thu, 21 Jun 2018 07:09:43 +0200
Klaus Wenninger wrote:
> On 06/21/2018 05:52 AM, Andrei Borzenkov wrote:
> > 21.06.2018 00:50, Digimer пишет:
> >> On 2018-06-20 05:46 PM, Jehan-Guillaume de Rorthais wrote:
> >>> On Wed, 20 Jun 2018 17:24:41 -0400
> >>> Digimer wrote:
> >>>
> Make s
23 matches
Mail list logo
