On 26/11/19 20:30 +0100, Jan Pokorný wrote:
> And yet another, this time late, stay-compatible type of problem with
> pacemaker vs. concurrent changes in build dependencies has popped up,
> this time with Inkscape. Whenever its 1.0 version is released,
> when with my ask
On 26/11/19 16:08 +0100, Jan Pokorný wrote:
> On 25/11/19 20:32 -0600, Ken Gaillot wrote:
>> The final release of Pacemaker version 2.0.3 is now available at:
>>
>> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.3
>
> For downstream and individual builders of the codebase
>
On Tue, 2019-11-26 at 08:31 +, BASDEN, ALASTAIR G. wrote:
> Hi,
>
> In our /var/log/messages, we are getting messages repeated every 5
> minutes:
> Nov 26 08:22:02 c6mds1 crmd[26950]: notice: State transition S_IDLE
> ->
> S_POLICY_ENGINE
> Nov 26 08:22:02 c6mds1 pengine[26949]: notice:
On Tue, 2019-11-26 at 08:40 +0100, Ulrich Windl wrote:
> Hi!
>
> I'm thinking about some mechanism that involves remote probing of
> some resource. As a result of such probing an attribute value would
> be set (like 0|1, maybe even multiple values).
> Is it possible to start a resource after the
On 25/11/19 20:32 -0600, Ken Gaillot wrote:
> The final release of Pacemaker version 2.0.3 is now available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.3
For downstream and individual builders of the codebase
==
Hello.
I am trying to setup a two-node cluster of SLES12SP4 servers. The two nodes
are named 'eagnmnmeqfc0', IP 56.76.161.34, and 'eagnmnmeqfc1', IP 56.76.161.35
The ha-cluster-init on fc0 went fine. It is set up for unicast, as multicast
is blocked on our networks.
The cluster-join on fc1
Hi,
In our /var/log/messages, we are getting messages repeated every 5
minutes:
Nov 26 08:22:02 c6mds1 crmd[26950]: notice: State transition S_IDLE ->
S_POLICY_ENGINE
Nov 26 08:22:02 c6mds1 pengine[26949]: notice: On loss of CCM Quorum:
Ignore
Nov 26 08:22:02 c6mds1 pengine[26949]: notice:
