On 22.04.2022 16:01, john tillman wrote:
>> On Fri, Apr 22, 2022 at 12:05 PM Tomas Jelinek
>> wrote:
>>>
>>> As discussed in other branches of this thread, you need to figure out
>>> why pacemaker is not starting. Even if one node is not running, corosync
>>> and pacemaker are expected to be able
> On Fri, Apr 22, 2022 at 12:05 PM Tomas Jelinek
> wrote:
>>
>> As discussed in other branches of this thread, you need to figure out
>> why pacemaker is not starting. Even if one node is not running, corosync
>> and pacemaker are expected to be able to start on the other node.
>
> Well, when tryi
On Fri, Apr 22, 2022 at 12:05 PM Tomas Jelinek wrote:
>
> As discussed in other branches of this thread, you need to figure out
> why pacemaker is not starting. Even if one node is not running, corosync
> and pacemaker are expected to be able to start on the other node.
Well, when trying to repro
Dne 21. 04. 22 v 17:26 john tillman napsal(a):
Dne 20. 04. 22 v 20:21 john tillman napsal(a):
On 20.04.2022 19:53, john tillman wrote:
I have a two node cluster that won't start any resources if only one
node
is booted; the pacemaker service does not start.
Once the second node boots up, the f
>>> "john tillman" schrieb am 21.04.2022 um 20:18 in
Nachricht
:
...
> Once the other node is started, something starts the pacemaker service.
Is the pacmemaker started, or does it begin to perform actions once it has a
quorum?
> pacemaker log starts filling up. journalctl ‑b sees plenty of pa
On Thu, Apr 21, 2022 at 8:18 PM john tillman wrote:
>
> > On 21.04.2022 18:26, john tillman wrote:
> >>> Dne 20. 04. 22 v 20:21 john tillman napsal(a):
> > On 20.04.2022 19:53, john tillman wrote:
> >> I have a two node cluster that won't start any resources if only one
> >> node
> >>>
