There is no fencing agent on this cluster and no shared storage.
-Eric
From: Strahil Nikolov
Sent: Friday, May 28, 2021 10:08 AM
To: Cluster Labs - All topics related to open-source clustering welcomed
; Eric Robinson
Subject: Re: [ClusterLabs] Cluster Stopped, No Messages?
what is your fenc
Shared storage is not what triggers the need for fencing. Coordinating
actions is what triggers the need. Specifically; If you can run resource
on both/all nodes at the same time, you don't need HA. If you can't, you
need fencing.
digimer
On 2021-05-28 1:19 p.m., Eric Robinson wrote:
> There is n
> -Original Message-
> From: Digimer
> Sent: Friday, May 28, 2021 12:43 PM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> ; Eric Robinson ; Strahil
> Nikolov
> Subject: Re: [ClusterLabs] Cluster Stopped, No Messages?
>
> Shared storage is not what triggers t
what is your fencing agent ?
Best Regards,Strahil Nikolov
On Thu, May 27, 2021 at 20:52, Eric Robinson wrote:
We found one of our cluster nodes down this morning. The server was up but
cluster services were not running. Upon examination of the logs, we found that
the cluster just stopp
Hello Team,
We have been recently running some tests on our Pacemaker clusters that involve two Pacemaker resources on two nodes respectively. The test case in which we are experiencing intermittent problems is one in which we bring down the Pacemaker resources on both nodes simultaneously. Now o
On 2021-05-28 3:08 p.m., Eric Robinson wrote:
>
>> -Original Message-
>> From: Digimer
>> Sent: Friday, May 28, 2021 12:43 PM
>> To: Cluster Labs - All topics related to open-source clustering welcomed
>> ; Eric Robinson ; Strahil
>> Nikolov
>> Subject: Re: [ClusterLabs] Cluster Stopped,
Most RA scripts are writen in bash.Usually you can change the shebang to
'!#/usr/bin/bash -x' or you can set trace_ra=1 via 'pcs resource update
RESOURCE trace_ra=1 trace_file=/somepath'.
If you don't define trace_file, it should create them in
/var/lib/heartbeat/trace_ra (based on memory -> so
I agree -> fencing is mandatory.
You can enable the debug logs by editing corosync.conf or
/etc/sysconfig/pacemaker.
In case simple reload doesn't work, you can set the cluster in global
maintenance, stop and then start the stack.
Best Regards,Strahil Nikolov
On Fri, May 28, 2021 at 22:13,
