Hi Team,
we are trying to building the latest 2.0.5 getting below error , can we know
reason for the same
https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5
$ ./autogen.sh
$ ./configure --prefix /root/pacemaker/
Above two command sucessed without error.
$ make -->
Hi Sathish,
It looks like it's trying to build pacemaker-remoted even though you
don't have the necessary prerequisites. I'll have to look into that for
the next release.
You could try installing the GnuTLS library first, or try commenting
out sbin_PROGRAMS in daemons/execd/Makefile.am.
On Fri,
Can someone help me with this?
Background:
"node01" is failing, and has been placed in "maintenance" mode. It
occasionally loses connectivity.
"node02" is able to run our resources
Consider the following messages from pacemaker.log on "node02", just after
"node01" has rejoined the cluster (per
29.01.2021 14:19, Ulrich Windl пишет:
> Hi!
>
> I'm having an odd failure using a systemd socket unit controlled by the
> cluster.
Why do you need socket unit to be controller by cluster in the first
place? The whole point of socket unit is to auto-start services on
access and that defeats
Hi!
I'm having an odd failure using a systemd socket unit controlled by the cluster.
(Personally I feel: "cluster and systemd: One resource controller too much".
But when you need to control a systemd unit...)
When the unit is active already, a start peration fails:
Jan 29 12:12:46 h16
>>> Andrei Borzenkov schrieb am 28.01.2021 um 18:30 in
Nachricht :
> 27.01.2021 22:03, Ken Gaillot пишет:
>>
>> With a group, later members depend on earlier members. If an earlier
>> member can't run, then no members after it can run.
>>
>> However we can't make the dependency go in both
>>> damiano giuliani schrieb am 28.01.2021 um
17:42
in Nachricht
:
> Hi Ulrich, thanks for the answer,
> as Ken explained me, there isnt any way to prevent earlier members from
> running
> if a later member has no available node,
> if no node is available for the failed member, then it will just
Hi again!
I had made a mistake: defining resource utilization with a name that doesn't
exist as node capacity/utilization (mistyped it).
The effect was that the resource was stopped, but unfortunately ptest did not
tell me why
("Insuffient node capacity for resource ...")
However I'd think
