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 still member of group pacemakerd
>
29.05.2019 11:12, Ulrich Windl пишет:
Jan Pokorný schrieb am 28.05.2019 um 16:31 in
> Nachricht
> <20190528143145.ga29...@redhat.com>:
>> On 27/05/19 08:28 +0200, Ulrich Windl wrote:
>>> I copnfigured ocf:pacemaker:NodeUtilization more or less for fun, and I
>> realized that the cluster
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 still member of group pacemakerd
(peer=rider.private, counter=0.2)
May 29 17:21:45 [51617] rider.private pacemakerd:
On Wed, 2019-05-29 at 11:42 +0100, lejeczek wrote:
> hi guys,
>
> I doing something which I believe is fairly simple, namely:
>
> $ pcs resource create HA-work9-win10-kvm VirtualDomain
> hypervisor="qemu:///system"
> config="/0-ALL.SYSDATA/QEMU_VMs/HA-work9-win10.qcow2"
> migration_transport=ssh
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 values inside Pacemaker,
> how about setting environment variables using
hi guys,
I doing something which I believe is fairly simple, namely:
$ pcs resource create HA-work9-win10-kvm VirtualDomain
hypervisor="qemu:///system"
config="/0-ALL.SYSDATA/QEMU_VMs/HA-work9-win10.qcow2"
migration_transport=ssh --disable
virt guest is good, runs in libvirth okey, yet
>>> Jan Pokorný schrieb am 28.05.2019 um 16:31 in
Nachricht
<20190528143145.ga29...@redhat.com>:
> On 27/05/19 08:28 +0200, Ulrich Windl wrote:
>> I copnfigured ocf:pacemaker:NodeUtilization more or less for fun, and I
> realized that the cluster rrepiorts no problems, but in syslog I have these
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 values inside Pacemaker, how
about setting environment variables using set_daemon_option() there?
For example, as PCMK_logficility
