<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Andrew, <br>I have send the core files attached to mail from Date: Thu, 20 Jun 2013 13:18:04 +0300. Unfortunately the mail server did not sent it.<br>Can you look on the mail server?<br><br>May be you miss my additional question:<br><br>Is it possible in Pacemaker to run one command and get the status of the node in the one value?<br>We do not want to parse the output of the command "pcs status" (run regEx on the output - since it can be changed).<br>We want to run one command that will return one value: online or offline (or standby).<br>Like<br><br><i> pcs status node node_name <br></i><br>Thank you for your help!<br> Best regards,<br> Michael<br><br><br><br><div>> From: andrew@beekhof.net<br>> Date: Fri, 21 Jun 2013 12:10:36 +1000<br>> To: pacemaker@oss.clusterlabs.org<br>> Subject: Re: [Pacemaker] Additional help with ClusterMon<br>> <br>> <br>> On 20/06/2013, at 8:49 PM, Michael Furman <michael_furman@hotmail.com> wrote:<br>> <br>> > Sending the second mail without attachments - the first one with with attachments :)<br>> <br>> I don't see the one with attachments.<br>> Did you paste the output from gdb in them?<br>> <br>> <br>> > <br>> > From: michael_furman@hotmail.com<br>> > To: pacemaker@oss.clusterlabs.org<br>> > Subject: RE: [Pacemaker] Additional help with ClusterMon<br>> > Date: Thu, 20 Jun 2013 13:18:04 +0300<br>> > <br>> > Andrew, Thanks for your help!<br>> > Please find the core files attached (3 from about 100).<br>> > <br>> > pcs status<br>> > ...<br>> > Version: 1.1.8-7.el6-394e906<br>> > <br>> > Installed:<br>> > corosync.x86_64 0:1.4.1-15.el6_4.1 <br>> > pacemaker.x86_64 0:1.1.8-7.el6<br>> > cman.x86_64 0:3.0.12.1-49.el6<br>> > <br>> > <br>> > Problematic configuration:<br>> > <br>> > 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"<br>> > <br>> > Regarding to my problem: is it possible in Pacemaker to run one command and get the status of the node in the one value?<br>> > We do not want to parse the output of the command "pcs status".<br>> > <br>> > Like <br>> > pcs status node node_name that will return online or offline (or standby).<br>> > <br>> > Thank you for your help!<br>> > Best regards,<br>> > Michael<br>> > <br>> > > From: andrew@beekhof.net<br>> > > Date: Wed, 19 Jun 2013 12:47:54 +1000<br>> > > To: pacemaker@oss.clusterlabs.org<br>> > > Subject: Re: [Pacemaker] Additional help with ClusterMon<br>> > > <br>> > > <br>> > > On 18/06/2013, at 11:58 PM, Michael Furman <michael_furman@hotmail.com> wrote:<br>> > > <br>> > > > I was able to run the ClusterMon agent.<br>> > > > <br>> > > > Couple of comments:<br>> > > > 1. When I uses ocf:pacemaker:ClusterMon it crashes a lot with the following core file:<br>> > > > <br>> > > > file core.22992<br>> > > > 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'<br>> > > <br>> > > Can you open that file up in gdb and run: where<br>> > > That will tell us why it is crashing.<br>> > > <br>> > > Also, what version is this?<br>> > > <br>> > > > <br>> > > > 2. I required to use ocf:heartbeat:ClusterMon. I found the way to configure it with pcs:<br>> > > > 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"<br>> > > > <br>> > > > <br>> > > > 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.<br>> > > <br>> > > Right, someone would have to implement that.<br>> > > <br>> > > > <br>> > > > <br>> > > > I want to do get the following events:<br>> > > > 1. On the node that become from active to stand-by the event that tell: “the node become from active to stand-by”<br>> > > > <br>> > > > 2. On node that become from standby to active the event that tell: “the node become from stand-by to active”<br>> > > > <br>> > > > Questions:<br>> > > > <br>> > > > 1. How it possible to configure ClusterMon to get such functionality?<br>> > > > 2. Is exists other agent that allows me to get events described above?<br>> > > > Thanks for your help,<br>> > > > Michael<br>> > > > <br>> > > > <br>> > > > <br>> > > > From: michael_furman@hotmail.com<br>> > > > To: pacemaker@oss.clusterlabs.org<br>> > > > Date: Fri, 14 Jun 2013 22:53:55 +0300<br>> > > > Subject: Re: [Pacemaker] Is it possible to add to add scripts when active / standby nodes are changed?<br>> > > > <br>> > > > Thank you for your hint!<br>> > > > I have found everything I need here:<br>> > > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_Explained/index.html#idm61451840<br>> > > > <br>> > > > <br>> > > > > From: andrew@beekhof.net<br>> > > > > Date: Fri, 14 Jun 2013 10:56:36 +1000<br>> > > > > To: pacemaker@oss.clusterlabs.org<br>> > > > > Subject: Re: [Pacemaker] Is it possible to add to add scripts when active / standby nodes are changed?<br>> > > > > <br>> > > > > Perhaps check out crm_mon --external-agent<br>> > > > > <br>> > > > > On 14/06/2013, at 12:47 AM, Michael Furman <michael_furman@hotmail.com> wrote:<br>> > > > > <br>> > > > > > Hi all!<br>> > > > > > I want to execute some actions when active / standby nodes are changed.<br>> > > > > > I want to do the following:<br>> > > > > > 1. Send SMTP mail<br>> > > > > > 2. Add message to syslog<br>> > > > > > 3. Execute my script<br>> > > > > > I want to do it in the following cases:<br>> > > > > > 1. On the node that become from active to standby<br>> > > > > > (May be some action will not work since something bad happens :) )<br>> > > > > > 2. On node that become from standby to active<br>> > > > > > <br>> > > > > > Is it possible to do with Pacemaker 1.1.8?<br>> > > > > > Thanks for your help!<br>> > > > > > Michael<br>> > > > > > _______________________________________________<br>> > > > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > > > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> > > > > > <br>> > > > > > Project Home: http://www.clusterlabs.org<br>> > > > > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > > > > > Bugs: http://bugs.clusterlabs.org<br>> > > > > <br>> > > > > <br>> > > > > _______________________________________________<br>> > > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> > > > > <br>> > > > > Project Home: http://www.clusterlabs.org<br>> > > > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > > > > Bugs: http://bugs.clusterlabs.org<br>> > > > <br>> > > > _______________________________________________ Pacemaker mailing list:Pacemaker@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<br>> > > > _______________________________________________<br>> > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> > > > <br>> > > > Project Home: http://www.clusterlabs.org<br>> > > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > > > Bugs: http://bugs.clusterlabs.org<br>> > > <br>> > > <br>> > > _______________________________________________<br>> > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> > > <br>> > > Project Home: http://www.clusterlabs.org<br>> > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > > Bugs: http://bugs.clusterlabs.org<br>> > _______________________________________________<br>> > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> > <br>> > Project Home: http://www.clusterlabs.org<br>> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > Bugs: http://bugs.clusterlabs.org<br>> <br>> <br>> _______________________________________________<br>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br>> <br>> Project Home: http://www.clusterlabs.org<br>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> Bugs: http://bugs.clusterlabs.org<br></div> </div></body>
</html>