Alex
> On 29.04.2024, at 09:56, Jan Friesse wrote:
>
> Hi,
> I will reply just to "sysadmin" question:
>
> On 26/04/2024 14:43, Alexander Eastwood via Users wrote:
>> Dear Reid,
> ...
>
>> Why does the corosync log say ’shutdown by sysadmin’ when
11:06:10.450 testcluster-c1 pacemakerd [1295869] (pcmk_child_exit) info: pacemaker-based[1295870] exited with status 0 (OK)Apr 23 11:06:10.458 testcluster-c1 pacemakerd [1295869] (pcmk_shutdown_worker) notice: Shutdown completeApr 23 11:06:10.458 testcluster-c1
Hi all,
I’m trying to get a better understanding of why our cluster - or specifically
corosync.service - entered a failed state. Here are all of the relevant
corosync logs from this event, with the last line showing when I manually
started the service again:
Apr 23 11:06:10 [1295854]
> not.
>
> Regards,
> Ulrich
>
> -Original Message-
> From: Users On Behalf Of Alexander Eastwood
> Sent: Wednesday, December 6, 2023 5:56 PM
> To: users@clusterlabs.org
> Subject: [EXT] [ClusterLabs] Prevent cluster transition when resource
> unav
Hello,
I administrate a Pacemaker cluster consisting of 2 nodes, which are connected
to each other via ethernet cable to ensure that they are always able to
communicate with each other. A network switch is also connected to each node
via ethernet cable and provides external access.
One of