On Sun, Feb 28, 2021 at 03:34:20PM +, Eric Robinson wrote:
> 001db02b rebooted. After it came back up, I tried it in the other direction.
>
> On node 001db02b, the command...
>
> # pcs stonith fence 001db02a
>
> ...produced output...
>
> Error: unable to fence '001db02a'.
>
> However,
> -Original Message-
> From: Users On Behalf Of Valentin Vidic
> Sent: Sunday, February 28, 2021 9:59 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] "Error: unable to fence '001db02a'" but It got
> fenced anyway
>
> On Sun, Feb 28, 2021 at 03:34:20PM +, Eric Robinson
On Sun, Feb 28, 2021 at 12:45:55PM +, Eric Robinson wrote:
> Colocation Constraints:
> p_fs_clust03 with ms_drbd0 (score:INFINITY)
> (id:colocation-p_fs_clust03-ms_drbd0-INFINITY)
> p_fs_clust04 with ms_drbd1 (score:INFINITY)
> (id:colocation-p_fs_clust04-ms_drbd1-INFINITY)
This
On Sun, Feb 28, 2021 at 05:54:26PM +, Eric Robinson wrote:
> I made the changes and tried again. Fencing took about 3.5 minutes and
> did not throw an error. Which raises the question, what happens if
> fencing takes more than 900 seconds? Will Pacemaker on the survivor
> node refuse to start
>>> Eric Robinson schrieb am 28.02.2021 um 16:34 in
Nachricht
> I just configured STONITH in Azure for the first time. My initial test went
> fine.
>
> On node 001db02a, the command...
>
> # pcs stonith fence 001db02b
>
> ...produced output...
>
> 001db02b fenced.
>
> 001db02b rebooted.
>>> Valentin Vidic schrieb am 28.02.2021 um
16:59
in Nachricht <20210228155921.gm29...@valentin-vidic.from.hr>:
> On Sun, Feb 28, 2021 at 03:34:20PM +, Eric Robinson wrote:
>> 001db02b rebooted. After it came back up, I tried it in the other
direction.
>>
>> On node 001db02b, the command...
>>> Eric Robinson schrieb am 26.02.2021 um 18:23 in
Nachricht
>> ‑Original Message‑
>> From: Digimer
>> Sent: Friday, February 26, 2021 10:35 AM
>> To: Cluster Labs ‑ All topics related to open‑source clustering welcomed
>> ; Eric Robinson
>> Subject: Re: [ClusterLabs] Our 2‑Node
>>> Reid Wahl schrieb am 27.02.2021 um 01:40 in Nachricht
:
> It's part of the resource-agents repository. When you build resource-agents
> from source, it should be created.
>
> https://github.com/ClusterLabs/resource-agents/blob/master/doc/dev-guides/ra
>
>>> Eric Robinson schrieb am 26.02.2021 um 17:19 in
Nachricht
> At 5:16 am Pacific time Monday, one of our cluster nodes failed and its mysql
> services went down. The cluster did not automatically recover.
>
> We're trying to figure out:
>
>
> 1. Why did it fail?
> 2. Why did it not
>>> Digimer schrieb am 26.02.2021 um 17:34 in Nachricht
<699432c7-89a6-41bf-c805-f4a7a0a4a...@alteeve.ca>:
> On 2021‑02‑26 11:19 a.m., Eric Robinson wrote:
>> At 5:16 am Pacific time Monday, one of our cluster nodes failed and its
>> mysql services went down. The cluster did not automatically
>>> Eric Robinson schrieb am 26.02.2021 um 19:58 in
Nachricht
>> -Original Message-
>> From: Users On Behalf Of Andrei
>> Borzenkov
>> Sent: Friday, February 26, 2021 11:27 AM
>> To: users@clusterlabs.org
>> Subject: Re: [ClusterLabs] Our 2-Node Cluster with a Separate Qdevice Went
Hi!
Here it's part of the resource agents:
v04:~ # which ocf-tester
/usr/sbin/ocf-tester
v04:~ # rpm -qf /usr/sbin/ocf-tester
resource-agents-4.3.018.a7fb5035-3.62.1.x86_64
Regards,
Ulrich
>>> Niveditha U schrieb am 26.02.2021 um 13:08 in
Nachricht
> Hi Ulrich,
>
> I do not have ocf-tester
On 01.03.2021 08:25, Niveditha U wrote:
> Hi Team,
>
> Can ocft be used in place of ocf-tester?
>
No, it's different tool.
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
On 27.02.2021 22:12, Andrei Borzenkov wrote:
> On 27.02.2021 17:08, Eric Robinson wrote:
>>
>> I agree, one node is expected to go out of quorum. Still the question is,
>> why didn't 001db01b take over the services? I just remembered that 001db01b
>> has services running on it, and those
We see in the log on 001db01a...
Feb 28 07:33:50 [61707] 001db02a.ccnva.localpengine: info:
master_color:ms_drbd1: Promoted 1 instances of a possible 1 to master
...and then...
Feb 28 07:33:50 [61707] 001db02a.ccnva.localpengine: notice: LogAction:
* Move
On Sun, Feb 28, 2021 at 07:45:27AM +, Strahil Nikolov wrote:
> As this is in Asure and they support shared disks , I think that a simple SBD
> could solve the stonith case.
Also fence_azure_arm: Azure Resource Manager :)
--
Valentin
___
Manage
> -Original Message-
> From: Users On Behalf Of Valentin Vidic
> Sent: Sunday, February 28, 2021 8:02 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Filesystem Resource Move Fails Because
> Underlying DRBD Resource Won't Move
>
> On Sun, Feb 28, 2021 at 12:45:55PM +, Eric
Beginning with this cluster status...
Cluster name: 001db02ab
Stack: corosync
Current DC: 001db02a (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with
quorum
Last updated: Sun Feb 28 07:24:31 2021
Last change: Sun Feb 28 07:19:51 2021 by hacluster via crmd on 001db02a
2 nodes configured
14
> -Original Message-
> From: Users On Behalf Of Valentin Vidic
> Sent: Sunday, February 28, 2021 4:37 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Our 2-Node Cluster with a Separate Qdevice Went
> Down Anyway?
>
> On Sun, Feb 28, 2021 at 07:45:27AM +, Strahil Nikolov
Oops, sorry, here are links to the text logs.
Node 001db02a: https://www.dropbox.com/s/ymbatz91x3y84wp/001db02a_log.txt?dl=0
Node 001db02b: https://www.dropbox.com/s/etq6mn460imdega/001db02b_log.txt?dl=0
-Eric
From: Users On Behalf Of Eric Robinson
Sent: Sunday, February 28, 2021 6:46 AM
To:
As this is in Asure and they support shared disks , I think that a simple SBD
could solve the stonith case.
Best Regards,Strahil Nikolov___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
Hi guys,
in case a developer(s) who might have something to do with
RPM builds for Centos read this:
-> $ dnf update -y
Last metadata expiration check: 0:44:10 ago on Sun 28 Feb
2021 10:43:03 GMT.
Error:
Problem 1: cannot install both
pacemaker-cluster-libs-2.0.5-8.el8.x86_64 and
I just configured STONITH in Azure for the first time. My initial test went
fine.
On node 001db02a, the command...
# pcs stonith fence 001db02b
...produced output...
001db02b fenced.
001db02b rebooted. After it came back up, I tried it in the other direction.
On node 001db02b, the
23 matches
Mail list logo
