Re: [ClusterLabs] crm_resource --wait

I've attached two files: 314 = after standby step 315 = after resource update On Wed, Oct 11, 2017 at 12:22 AM, Ken Gaillot wrote: > On Tue, 2017-10-10 at 15:19 +1000, Leon Steffens wrote: > > Hi Ken, > > > > I managed to reproduce this on a simplified version of the

Re: [ClusterLabs] corosync service not automatically started

Ken Gaillot napsal(a): On Tue, 2017-10-10 at 12:24 +0200, Václav Mach wrote: On 10/10/2017 11:40 AM, Valentin Vidic wrote: On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6

Re: [ClusterLabs] corosync service not automatically started

Václav Mach napsal(a): On 10/10/2017 11:40 AM, Valentin Vidic wrote: On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto allow-hotplug or dhcp

Re: [ClusterLabs] corosync service not automatically started

On Tue, 2017-10-10 at 12:24 +0200, Václav Mach wrote: > On 10/10/2017 11:40 AM, Valentin Vidic wrote: > > On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote: > > > # The primary network interface > > > allow-hotplug eth0 > > > iface eth0 inet dhcp > > > # This is an autoconfigured IPv6

Re: [ClusterLabs] crm_resource --wait

On Tue, 2017-10-10 at 15:19 +1000, Leon Steffens wrote: > Hi Ken, > > I managed to reproduce this on a simplified version of the cluster, > and on Pacemaker 1.1.15, 1.1.16, as well as 1.1.18-rc1 > The steps to create the cluster are: > > pcs property set stonith-enabled=false > pcs property set

Re: [ClusterLabs] if resourceA starts @nodeA then start resource[xy] @node[xy]

On 26/09/17 13:15, Klaus Wenninger wrote: On 09/26/2017 02:06 PM, lejeczek wrote: hi fellas can something like in the subject pacemaker do? And if yes then how to do it? You could bind ResourceA to nodeA and resource[xy] to node[xy] via location constraints. Afterwards you could make

Re: [ClusterLabs] corosync service not automatically started

On 10/10/2017 11:40 AM, Valentin Vidic wrote: On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto allow-hotplug or dhcp could be causing problems.

Re: [ClusterLabs] corosync service not automatically started

On Tue, Oct 10, 2017 at 11:26:24AM +0200, Václav Mach wrote: > # The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > # This is an autoconfigured IPv6 interface > iface eth0 inet6 auto allow-hotplug or dhcp could be causing problems. You can try disabling corosync and

Re: [ClusterLabs] corosync service not automatically started

On 10/10/2017 11:04 AM, Valentin Vidic wrote: On Tue, Oct 10, 2017 at 10:35:17AM +0200, Václav Mach wrote: Oct 10 10:27:05 r1nren.et.cesnet.cz corosync[709]: [QB] Denied connection, is not ready (709-1337-18) Oct 10 10:27:06 r1nren.et.cesnet.cz corosync[709]: [QB] Denied

Re: [ClusterLabs] corosync service not automatically started

On Tue, Oct 10, 2017 at 10:35:17AM +0200, Václav Mach wrote: > Oct 10 10:27:05 r1nren.et.cesnet.cz corosync[709]: [QB] Denied > connection, is not ready (709-1337-18) > Oct 10 10:27:06 r1nren.et.cesnet.cz corosync[709]: [QB] Denied > connection, is not ready (709-1337-18) > Oct 10

[ClusterLabs] corosync service not automatically started

Hello, I'm working on a two node cluster. The nodes are r1nren (r1) and r2nren (r2). There are some resources at the moment, but I think it's not important for this problem. Both nodes are virtual servers running on vmware. Both nodes are running debian strech, I'm using corosync and

[ClusterLabs] ClusterMon mail notification - does not work

Hi all. I've just tried to add an e-mail notification for my cluster built with pacemaker, but ClusterMon seems doesn't work as expected. I have ssmtp configured on ubuntu 16.04 I configured cluster monitor by crmsh: primitive cluster_mon ocf:pacemaker:ClusterMon \ params