Re: [ClusterLabs] [ClusterLab] : Unable to bring up pacemaker

On 04/27/2016 11:25 AM, emmanuel segura wrote: > you need to use pcs to do everything, pcs cluster setup and pcs > cluster start, try to use the redhat docs for more information. Agreed -- pcs cluster setup will create a proper corosync.conf for you. Your corosync.conf below uses corosync 1

[ClusterLabs] Antw: Re: Coming in 1.1.15: Event-driven alerts

>>> Kristoffer Grönlund schrieb am 27.04.2016 um 12:12 in Nachricht <87twinl5sb@krigpad.kri.gs>: > Ken Gaillot writes: > >> The most prominent feature will be Klaus Wenninger's new implementation >> of event-driven alerts -- the ability to call

[ClusterLabs] crmsh release 2.1.6

Hi everyone, (As I was preparing this, I realised that I wasn't subscribed to the developers list. Oops. To avoid this mail getting stuck in a moderation filter, I'm just sending it to the users list. I assume everyone in the developers list is here as well anyway.) I'm happy to present version

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

Hi Dmitri, On Tue, Apr 26, 2016 at 10:20:45AM -0500, Dmitri Maziuk wrote: > On 2016-04-26 00:58, Klaus Wenninger wrote: > > >But what you are attempting doesn't sound entirely proprietary. > >So once you have something that looks like it might be useful > >for others as well let the community

[ClusterLabs] [ClusterLab] : Unable to bring up pacemaker

Dear All, I m trying to use pacemaker and corosync for the clustering requirement that came up recently. We have cross compiled corosync, pacemaker and pcs(python) for ppc environment (Target board where pacemaker and corosync are supposed to run) I m having trouble bringing up pacemaker in that

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Hi All, We have a request for a new SNMP function. The order of traps is not right. The turn of the trap is not sometimes followed. This is because the handling of notice carries out "path" in async. I think that it is necessary to wait for completion of the practice at "path" unit of

Re: [ClusterLabs] Antw: Re: kvm live migration, resource moving

Hi List, I have two major problems related to the VirtualDomain live migration and failover in general. I'm using Pacemaker 1.1.8, which is very stable and used to do everything right to me. 1. Live migration during failover (node standby or shutdown) is ok, but during failback, the VMs

Re: [ClusterLabs] dlm_controld 4.0.4 exits when crmd is fencing another node

David Teigland writes: > On Tue, Apr 26, 2016 at 09:57:06PM +0200, Valentin Vidic wrote: > >> The bug is caused by the missing braces in the expanded if >> statement. >> >> Do you think we can get a new version out with this patch as the >> fencing in 4.0.4 does not work

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Klaus Wenninger writes: >> >> alert alert-1 /srv/pacemaker/pcmk_alert_sample.sh \ >> to /var/log/cluster-alerts.log > Are (and if yes how) you planning to handle multiple recipients? Yes, just put multiple "to" statements after each other: alert alert-1

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/27/2016 12:12 PM, Kristoffer Grönlund wrote: > Ken Gaillot writes: > >> The most prominent feature will be Klaus Wenninger's new implementation >> of event-driven alerts -- the ability to call scripts whenever >> interesting events occur (nodes joining/leaving,

Re: [ClusterLabs] Simple clarification regarding pacemaker

On 04/26/2016 09:09 PM, K Aravind wrote: > Thank you for the quick responses :) > I starting to understand :) > One more quick question. > Let's say I have a 2 node cluster with stonith-enabled=false and no > quorum policy = ignore > And master-max=1 > Now connection between nodes went down. >