On 30/05/2019 14:06, Jan Pokorný wrote:
> On 30/05/19 11:01 +0100, lejeczek wrote:
>> On 29/05/2019 21:04, Ken Gaillot wrote:
>>> On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
and:
$ systemctl status -l pacemaker.service
● pacemaker.service - Pacemaker High Availability
On 30/05/19 11:01 +0100, lejeczek wrote:
> On 29/05/2019 21:04, Ken Gaillot wrote:
>> On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
>>> and:
>>> $ systemctl status -l pacemaker.service
>>> ● pacemaker.service - Pacemaker High Availability Cluster Manager
>>>Loaded: loaded
On 29/05/2019 21:04, Ken Gaillot wrote:
> On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
>> hi guys,
>>
>> I have a 3-nodes cluster but one node is a freaking mystery to me. I
>> see
>> this:
>>
>> May 29 17:21:45 [51617] rider.private pacemakerd: info:
>> pcmk_cpg_membership:Node 3
On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
> hi guys,
>
> I have a 3-nodes cluster but one node is a freaking mystery to me. I
> see
> this:
>
> May 29 17:21:45 [51617] rider.private pacemakerd: info:
> pcmk_cpg_membership:Node 3 still member of group pacemakerd
>
hi guys,
I have a 3-nodes cluster but one node is a freaking mystery to me. I see
this:
May 29 17:21:45 [51617] rider.private pacemakerd: info:
pcmk_cpg_membership: Node 3 still member of group pacemakerd
(peer=rider.private, counter=0.2)
May 29 17:21:45 [51617] rider.private pacemakerd: