Re: [ClusterLabs] Fwd: FW: heartbeat can monitor virtual IP alive or not .

On Thu, Apr 21, 2016 at 01:18:13AM +0800, fu ml wrote: > Ha.cf: > > The question is we want heartbeat monitor virtual IP, > > If this virtual IP on Linux01 can’t ping or respond , > > We want Linux02 auto take over this service IP Regardless of Linux01’s > Admin IP is alive or not, > > > > We

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

On 2016-04-27T12:10:10, Klaus Wenninger wrote: > > Having things in ARGV[] is always risky due to them being exposed more > > easily via ps. Environment variables or stdin appear better. > What made you assume the recipient is being passed as argument? > > The environment

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

Hi Klaus, Because the script is performed the effectiveness of in async, I think that it is difficult to set "uptime" by the method of the sample. After all we may request the transmission of the order. #The patch before mine only controls a practice turn of the async and is not a thing giving

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

On 04/28/2016 08:33 AM, Ulrich Windl wrote: > Hi! > > I wonder: would passing the CIB generation (like 1.6.122) or a (local?) event > sequence number to the notification script (SNMP trap) help? CRM_alert_node_sequence is there already but as the name says it is just a reference within one node

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

Thanks Ken and Emmanuel. Its a big endian machine. I will try with running "pcs cluster setup" and "pcs cluster start" Inside cluster.py, "service pacemaker start" and "service corosync start" are executed to bring up pacemaker and corosync. Those service scripts and the infrastructure needed to

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

Ulrich Windl writes: > IMHO it reads too much like the XML (i.e. nobody understands it unless he > knows the meaning of the XML behind). Do you have any suggestion as to how that could be improved? So far we've tried not to stray too far from the XML with the

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

Hi! I wonder: would passing the CIB generation (like 1.6.122) or a (local?) event sequence number to the notification script (SNMP trap) help? Regards, Ulrich >>> Klaus Wenninger schrieb am 27.04.2016 um 20:14 in Nachricht <57210183.6050...@redhat.com>: > On 04/27/2016

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

On 04/27/2016 11:01 AM, Dejan Muhamedagic wrote: ... I failed to >> convince Andrew that wget'ing http://localhost/server-status/ is a >> wrong thing to do in the first place (apache RA). > > I'm not sure why would it be wrong, but neither can I vouch that > there's no better way to do a basic

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

On 04/27/2016 05:28 PM, Sriram wrote: > 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 >