>
> That is really not a pacemaker problem and is better suited for general
> systemd troubleshooting resource. But as you have been already
> requested, show at least "systemctl status pacemaker.service" and
> "systemctl status drbd.service" when pacemaker does not start.
>
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
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
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
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
>
> 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
>> is booted; the pacemaker service does not start.
>>
>>
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
> is booted; the pacemaker service does not start.
>
> Once the
> 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 first node will start
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 first node will start pacemaker and
the
> On Wed, 2022-04-20 at 12:53 -0400, 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 first node will start pacemaker
>> and the
>> resources are started.
> 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 first node will start pacemaker and
>> the
>> resources are started. All is well.
On Wed, 2022-04-20 at 12:53 -0400, 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 first node will start pacemaker
> and the
> resources are started. All is
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 first node will start pacemaker and the
> resources are started. All is well. But I
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 first node will start pacemaker and the
resources are started. All is well. But I would like the resources to
start when the first node
15 matches
Mail list logo
