Hello Ulrich,
Thank you for your reply. I'm sorry my message didn't have the
configuration explained. I try not to flood emails with information
that many may not care about and prefer to reply to the curious with
specific answers. I'll add more information to my reply to your next
message.
Best regards,
John
On 2026-11-02 05:36, Windl, Ulrich via Users wrote:
HI!
As you know the time when you pulled the cable, just restrict the log
entries after that event until the time when pacemakerd died.
Apart from that if the network cable is the only connection, it may
work as designed to avoid a split brain syndrome.
I don't know your configuration, and you did not explain it.
Kind regards,
Ulrich Windl
-----Original Message-----
From: Users <[email protected]> On Behalf Of john tillman
Sent: Thursday, October 22, 2026 9:56 PM
To: Cluster Labs - All topics related to open-source clustering
welcomed
<[email protected]>
Subject: [EXT] [EXT] Re: [ClusterLabs] pacemaker&corosync services
shutting
off after the network cable is disconnected
Greetings Chris/All,
I've had some time to get back to this issue. It is still occurring.
To refresh, I have pacemaker services running in a VM. When I pull
out
the network cable from the associated hypervisor the pacemakerd
process
will exit.
I think it would be helpful if I can provide the pacemaker.log file
from
when this issue occurs. What would be the best way to provide that
log
file? It's ~114KB and about 753 lines long.
-John
On 2026-09-14 10:07, JT wrote:
> Chris,
> Thanks for trying this. My experience has been with the cluster
> services running on VMs, when the cable to the hypervisor is pulled.
> The hypervisor only had one VM with cluster services on it. The
> remaining cluster nodes were on other VMs on other hypervisor, all on
> the same subnet.
>
> I'm not sure if the nmcli command being run on the VM would reproduce
> the same effect?
>
> -John
>
> On September 11, 2026 4:12:43 PM EDT, Chris Lumens
> <[email protected]> wrote:
>
>>> pacemaker 2.1.9-1 On Rhel 9.6 - No problem with network
>>> isolation
>>> pacemaker 2.1.10-2 On Rhel 9.8 - Problem I described
>>
>> I've been trying to reproduce this today, but so far no luck. I had
>> an idea which patch might be to blame, so maybe there's another
>> patch at fault that I haven't tried yet. Alternatively, perhaps
>> there's something about how I am taking down the network on my VM
>> (nmcli device down) that results in different behavior than how you
>> are losing the network.
>>
>> - Chris
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
