Re: [ClusterLabs] Antw: Re: Antw: Re: why is node fenced ?

- On Aug 14, 2019, at 8:25 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: > But why do the eth interfaces on both nodes come up the same second > (2019-08-09T17:42:19)? > The respective eth's of the two bonds of the two hosts are connected directly to each other. Just a

[ClusterLabs] Q: "Re-initiated expired calculated failure"

(subject changed for existing thread) Hi! After I had thought the problem with the sticky failed monitor was solved eventually, I realized that I'm getting a message that I don't really understand after each cluster recheck interval: pengine[7280]: notice: Re-initiated expired calculated

[ClusterLabs] Antw: Re: Antw: Re: why is node fenced ?

>>> "Lentes, Bernd" schrieb am 13.08.2019 um 16:03 in Nachricht <854237493.2026097.1565705038122.javamail.zim...@helmholtz-muenchen.de>: > > - On Aug 13, 2019, at 3:14 PM, Ulrich Windl > ulrich.wi...@rz.uni-regensburg.de wrote: > >> You said you booted the hosts sequentially. From the

Re: [ClusterLabs] why is node fenced ?

- On Aug 13, 2019, at 1:19 AM, kgaillot kgail...@redhat.com wrote: > > The key messages are: > > Aug 09 17:43:27 [6326] ha-idg-1 crmd: info: crm_timer_popped: > Election > Trigger (I_DC_TIMEOUT) just popped (2ms) > Aug 09 17:43:27 [6326] ha-idg-1 crmd: warning:

[ClusterLabs] [Announce] clufter v0.77.2 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.77.2 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] why is node fenced ?

On Wed, 2019-08-14 at 11:57 +0200, Lentes, Bernd wrote: > > - On Aug 13, 2019, at 1:19 AM, kgaillot kgail...@redhat.com > wrote: > > > > > > The key messages are: > > > > Aug 09 17:43:27 [6326] ha-idg-1 crmd: info: > > crm_timer_popped: Election > > Trigger (I_DC_TIMEOUT) just

Re: [ClusterLabs] Q: "Re-initiated expired calculated failure"

On Wed, 2019-08-14 at 10:24 +0200, Ulrich Windl wrote: > (subject changed for existing thread) > > Hi! > > After I had thought the problem with the sticky failed monitor was > solved > eventually, I realized that I'm getting a message that I don't really > understand after each cluster recheck