Hi All,
I'm running Pacemaker 2.0.1 on a cluster containing two nodes; one master and
one slave. I have a main master/slave resource (m_main_system), a group of
resources that run in active-active mode (active_active - i.e. run on both
nodes), and a group that runs in active-disabled mode
On Wed, 2019-05-29 at 09:23 -0500, Ken Gaillot wrote:
> On Wed, 2019-05-29 at 16:53 +0900, 飯田雄介 wrote:
> > Hi Ken and Jan,
> >
> > Thank you for your comment.
> >
> > I understand that solusion is to set PCMK_logfile in the sysconfig
> > file.
> >
> > As a permanent fix, if you use the default
Source code for the third (and likely final) release candidate for
Pacemaker version 2.0.2 is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.2-rc3
This fixes regressions found in rc2. I expect this will become the
final release next week. For details,
On 20/05/19 14:35 +0200, Jan Pokorný wrote:
> On 20/05/19 08:28 +0200, Ulrich Windl wrote:
>>> One network interface is gone for a short period. But it's in a
>>> bonding device (round-robin), so the connection shouldn't be lost.
>>> Both nodes are connected directly, there is no switch in
[forwarding to respective upstream list, this has little to do with
systemd, I suggest following up only there, detaching from systemd ML]
On 29/05/19 17:23 +0100, lejeczek wrote:
> something I was hoping one expert could shed bit more light onto - I
> have a pacemaker cluster composed of three
On 30/05/19 11:01 +0100, lejeczek wrote:
> On 29/05/2019 21:04, Ken Gaillot wrote:
>> On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
>>> and:
>>> $ systemctl status -l pacemaker.service
>>> ● pacemaker.service - Pacemaker High Availability Cluster Manager
>>>Loaded: loaded
On 29/05/2019 21:04, Ken Gaillot wrote:
> On Wed, 2019-05-29 at 17:28 +0100, lejeczek wrote:
>> hi guys,
>>
>> I have a 3-nodes cluster but one node is a freaking mystery to me. I
>> see
>> this:
>>
>> May 29 17:21:45 [51617] rider.private pacemakerd: info:
>> pcmk_cpg_membership:Node 3
