[ClusterLabs] Troubleshooting Faulty Networks / Heartbeat Rings

and finally to tune it's configuration parameters and trouble shoot it adequately ? It seems there is little documentation on this topic (besides the source code). Could somebody please point me to some useful sources of information ? Regards, Martin Sch

Re: [ClusterLabs] Corosync ring shown faulty between healthy nodes & networks (rrp_mode: passive)

et the way to go in the future then ? Regards, Martin Schlegel > Jan Friesse hat am 7. Oktober 2016 um 11:28 geschrieben: > > Martin Schlegel napsal(a): > > > Thanks for the confirmation Jan, but this sounds a bit scary to me ! > > > > Spinning this experiment a b

Re: [ClusterLabs] Corosync ring shown faulty between healthy nodes & networks (rrp_mode: passive)

. Regards, Martin Schlegel > Jan Friesse hat am 5. Oktober 2016 um 09:01 geschrieben: > > Martin, > > > Hello all, > > > > I am trying to understand why the following 2 Corosync heartbeat ring > > failure > > scenarios > > I have been testing and ho

Re: [ClusterLabs] Corosync ring shown faulty between healthy nodes & networks (rrp_mode: passive)

. Regards, Martin Schlegel > Jan Friesse hat am 5. Oktober 2016 um 09:01 geschrieben: > > Martin, > > > Hello all, > > > > I am trying to understand why the following 2 Corosync heartbeat ring > > failure > > scenarios > > I have been testing and ho

[ClusterLabs] Corosync ring shown faulty between healthy nodes & networks (rrp_mode: passive)

xperiment 1. B and C can still communicate with each other over both NICs, so why are B and C not displaying a "no faults" status for ring id 0 and 1 just like in experiment 2. when node A is completely unreachable ? Regards, Martin Schlegel ___

Re: [ClusterLabs] Users Digest, Vol 18, Issue 42

On 07/21/2016 08:49 AM, Ulrich Windl wrote: Ken Gaillot schrieb am 19.07.2016 um 16:17 in Nachricht > > : > > > > [...] > > >> You're right -- if not told otherwise, Pacemaker will query the device>> > >> for the target list. In this case, the output of "stonith_admin -l" > > > In sl

Re: [ClusterLabs] Pacemaker not always selecting the right stonith device

s found p_ston_pg3 p_ston_pg2 pg2 == 2 devices found p_ston_pg3 p_ston_pg1 pg3 == 2 devices found p_ston_pg1 p_ston_pg2 > Andrei Borzenkov hat am 20. Juli 2016 um 08:26 > geschrieben: > > On Tue, Jul 19, 2016 at 6:33 PM, Martin Schlegel wrote: > >> > [...]

Re: [ClusterLabs] Pacemaker not always selecting the right stonith device

> Date: Tue, 19 Jul 2016 08:52:19 -0500 > From: Ken Gaillot > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Pacemaker not always selecting the right > stonith device > Message-ID: > Content-Type: text/plain; charset=utf-8 > > On 07/18/2016 05:5

Re: [ClusterLabs] Antw: Re: Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

> Ulrich Windl hat am 19. Juli 2016 um 08:41 > geschrieben: > > >>> Martin Schlegel schrieb am 19.07.2016 um 00:51 in > Nachricht > <301244266.332724.5ea3ddc5-55ea-43b0-9a1b-22ebb1dcafd2.open-xchange@email.1und1. > e>: > > > Thanks Jan ! > >

Re: [ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

interface was assigned the IP-address. For now we have added some code to the Corosync runlevel scripts that waits for a certain amount for whatever bindnetaddr-IPs had been configured in /etc/corosync/corosync.conf . Cheers, Martin Schlegel > Jan Friesse hat am 16. Juni 2016 um 17:5

[ClusterLabs] Pacemaker not always selecting the right stonith device

Hello all I cannot wrap my brain around what's going on here ... any help would prevent me from fencing my brain  =:-D Problem: When completely network isolating a node, i.e. pg1 - sometimes a different node gets fenced instead, i.e. pg3 ... in this case I see a syslog message like this indica

Re: [ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

se 4x physical network interfaces with 2x bond'ed into a public (bond1) and 2x bond'ed into a private network (bond0). Could this have anything to do with it ? Regards, Martin Schlegel ___ >From /etc/network/interfaces, i.e. auto bond0 iface bond0 inet static #pre-up /sbi

[ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

1 briefly shows "no faults" but goes back to "FAULTY" seconds later. Regards, Martin Schlegel _ root@pg1:~# corosync-cfgtool -s Printing ring status. Local node ID 1 RING ID 0 id = A.B.C1.5 status = ring 0 ac

[ClusterLabs] Opt-in cluster shows resources stopped where no nodes should be considered

alog1 \ rule #uname eq pgalog2 location l_pgs_resources { cl_pgsServices1 ms_pgsqln p_pgsBackupjob pgalog1 pgalog2 } resource-discovery=exclusive \ rule #uname eq pg1 \ rule #uname eq pg2 \ rule #uname eq pg3 [...] property cib-bootstrap-options: \

[ClusterLabs] crm_mon change in behaviour PM 1.1.12 -> 1.1.14: crm_mon -XA filters #health.* node attributes

extensive and clutters up the output it would make sense to allow a user-defined filter for node attributes in generalRegards,Martin Schlegel ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project

[ClusterLabs] crm_mon change in behaviour PM 1.1.12 -> 1.1.14: crm_mon -XA filters #health.* node attributes

and clutters up the output it would make sense to allow a user-defined filter for node attributes in generalRegards,Martin Schlegel ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http