[Pacemaker] Additional help with ClusterMon

Michael Furman michael_furman at hotmail.com
Thu Jun 20 10:49:13 UTC 2013


Sending the second mail without attachments - the first one with with attachments :)

From: michael_furman at hotmail.com
To: pacemaker at oss.clusterlabs.org
Subject: RE: [Pacemaker] Additional help with ClusterMon
Date: Thu, 20 Jun 2013 13:18:04 +0300




Andrew, Thanks for your help!
Please find the core files attached (3 from about 100).

pcs status
...
Version: 1.1.8-7.el6-394e906



Installed:

  corosync.x86_64
0:1.4.1-15.el6_4.1 
  pacemaker.x86_64 0:1.1.8-7.el6



  cman.x86_64
0:3.0.12.1-49.el6



Problematic configuration:

pcs resource create
ClusterMonScript1  ocf:pacemaker:ClusterMon params user="root"
update="1" extra_options="-E /usr/local/bin/example.sh -e
127.0.0.1" 


Regarding to my problem: is it possible in Pacemaker to run one command and get the status of the node in the one value?
We do not want to parse the output  of the command "pcs status".

Like 
pcs status node node_name that will return online or offline (or standby).

Thank you for your help!
Best regards,
    Michael

> From: andrew at beekhof.net
> Date: Wed, 19 Jun 2013 12:47:54 +1000
> To: pacemaker at oss.clusterlabs.org
> Subject: Re: [Pacemaker] Additional help with ClusterMon
> 
> 
> On 18/06/2013, at 11:58 PM, Michael Furman <michael_furman at hotmail.com> wrote:
> 
> > I was able to run the ClusterMon agent.
> > 
> > Couple of comments:
> > 1.       When I uses ocf:pacemaker:ClusterMon it crashes a lot with the following core file:
> > 
> > file core.22992
> > core.22992: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/sbin/crm_mon -p /tmp/ClusterMon_ClusterMon.pid -d -i 0 -E /usr/local/bin/e'
> 
> Can you open that file up in gdb and run:  where
> That will tell us why it is crashing.
> 
> Also, what version is this?
> 
> >  
> > 2.       I required to use ocf:heartbeat:ClusterMon. I found the way to configure it with pcs:
> > pcs resource create ClusterMonScript1  ocf:heartbeat:ClusterMon params user="root" update="30" extra_options="-E /usr/local/bin/example.sh" op monitor on-fail="restart" interval="20"
> > 
> > 
> > Unfortunately, ClusterMon get only resource oriented event. In addition, it does not get event on the node that become stand-by and get the event only on the node that become master.
> 
> Right, someone would have to implement that.
> 
> > 
> >  
> > I want to do get the following events:
> > 1.       On the node that become from active to stand-by the event that tell: “the node become from active to stand-by”
> > 
> > 2.       On node that become from standby to active the event that tell: “the node become from stand-by to active”
> > 
> > Questions:
> > 
> > 1.       How it possible to configure ClusterMon to get such functionality?
> > 2.       Is exists other agent that allows me to get events described above?
> > Thanks for your help,
> > Michael
> >  
> > 
> > 
> > From: michael_furman at hotmail.com
> > To: pacemaker at oss.clusterlabs.org
> > Date: Fri, 14 Jun 2013 22:53:55 +0300
> > Subject: Re: [Pacemaker] Is it possible to add to add scripts when active / standby nodes are changed?
> > 
> > Thank you for your hint!
> > I have found everything I need here:
> > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_Explained/index.html#idm61451840
> > 
> > 
> > > From: andrew at beekhof.net
> > > Date: Fri, 14 Jun 2013 10:56:36 +1000
> > > To: pacemaker at oss.clusterlabs.org
> > > Subject: Re: [Pacemaker] Is it possible to add to add scripts when active /	standby nodes are changed?
> > > 
> > > Perhaps check out crm_mon --external-agent
> > > 
> > > On 14/06/2013, at 12:47 AM, Michael Furman <michael_furman at hotmail.com> wrote:
> > > 
> > > > Hi all!
> > > > I want to execute some actions when active / standby nodes are changed.
> > > > I want to do the following:
> > > > 1. Send SMTP mail
> > > > 2. Add message to syslog
> > > > 3. Execute my script
> > > > I want to do it in the following cases:
> > > > 1. On the node that become from active to standby
> > > > (May be some action will not work since something bad happens :) )
> > > > 2. On node that become from standby to active
> > > > 
> > > > Is it possible to do with Pacemaker 1.1.8?
> > > > Thanks for your help!
> > > > Michael
> > > > _______________________________________________
> > > > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > > > 
> > > > Project Home: http://www.clusterlabs.org
> > > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > > > Bugs: http://bugs.clusterlabs.org
> > > 
> > > 
> > > _______________________________________________
> > > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > > 
> > > Project Home: http://www.clusterlabs.org
> > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > > Bugs: http://bugs.clusterlabs.org
> > 
> > _______________________________________________ Pacemaker mailing list: Pacemaker at oss.clusterlabs.orghttp://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started:http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > 
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130620/3c8ca7f3/attachment.htm>


More information about the Pacemaker mailing list