pacemaker-controld [123697] (do_log) info: Input
I_ELECTION_DC received in state S_ELECTION from election_win_cb
This is a cluster with 2 nodes, gopher11 and gopher12.
Am I misreading that?
thanks,
Olaf
From: Ken Gaillot
Sent: Monday, January 29, 2024
en Gaillot
Sent: Monday, January 29, 2024 10:51 AM
To: Cluster Labs - All topics related to open-source clustering welcomed
Cc: Faaland, Olaf P.
Subject: Re: [ClusterLabs] controlling cluster behavior on startup
On Mon, 2024-01-29 at 18:05 +0000, Faaland, Olaf P. via Users wrote:
> Hi,
&g
Hi,
I have configured clusters of node pairs, so each cluster has 2 nodes. The
cluster members are statically defined in corosync.conf before corosync or
pacemaker is started, and quorum {two_node: 1} is set.
When both nodes are powered off and I power them on, they do not start
pacemaker at
zilla.redhat.com/show_bug.cgi?id=1176018
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1459503
Regards,
Tomas
Dne 22.2.2018 v 20:50 Faaland, Olaf P. napsal(a):
> Hi,
>
>
> I see when I invoke
>
>
> # pcs cluster setup --force --local --name
>
>
>
> It reports "
Hi,
I see when I invoke
# pcs cluster setup --force --local --name
It reports "Removing all cluster configuration files..." and true to its word,
removes /etc/pacemaker/authkey.
My cluster configuration depends on nodes running pacemaker_remote and so I
depend on the authkey to
