<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Dejan,<br></blockquote><div><br></div><div>I tried with lrmadmin -M lsb httpd NULL and was able to get the meta-data.</div>
<div><br></div><div>I was able to add a resource from lrmadmin but i cannot see that resource in crm shell.</div><div><br></div><div>Many Thanks</div><div>Vishal</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Message: 1<br>
Date: Tue, 23 Oct 2012 13:48:24 +0200<br>
From: Dejan Muhamedagic <<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
Subject: Re: [Pacemaker] Pacemaker Digest, Vol 59, Issue 57<br>
Message-ID: <20121023114823.GA19526@walrus.homenet><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
On Tue, Oct 23, 2012 at 10:18:36AM +0530, vishal kumar wrote:<br>
> Hello Florian,<br>
><br>
> Thanks for the help.<br>
><br>
> I tried with crm ra meta sshd lsb but it gave me the same meta-data error.<br>
><br>
> The problem is while trying to add a lsb resource from crm shell, like<br>
> httpd as i am using rhel it gives the following error<br>
> ERROR: lsb:httpd: could not parse meta-data:<br>
> ERROR: lsb:httpd: no such resource agent<br>
><br>
> the httpd package is installed and i have a httpd file /etc/init.d<br>
> directory. I am unable to add any resource which in /etc/init.d directory.<br>
<br>
Do you have cluster-glue installed? And is pacemaker running?<br>
lrmadmin (part of cluster-glue) gets the meta-data from lrmd. You<br>
can try it by hand like this:<br>
<br>
lrmadmin -M lsb httpd NULL<br>
<br>
Thanks,<br>
<br>
Dejan<br>
<br>
> Many thanks<br>
> Vishal<br>
><br>
><br>
> Message: 1<br>
> > Date: Mon, 22 Oct 2012 17:53:23 +0530<br>
> > From: vishal kumar <<a href="mailto:vishal.kanojwar@gmail.com">vishal.kanojwar@gmail.com</a>><br>
> > To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> > Subject: [Pacemaker] lsb: could not parse meta-data<br>
> > Message-ID:<br>
> > <CANz=<br>
> > <a href="mailto:RdkSq4t-SbbF%2BKBNWoB2fGR7xu7G6MRUgBPfZASBvNPdnA@mail.gmail.com">RdkSq4t-SbbF+KBNWoB2fGR7xu7G6MRUgBPfZASBvNPdnA@mail.gmail.com</a>><br>
> > Content-Type: text/plain; charset="iso-8859-1"<br>
> ><br>
> > Hi<br>
> ><br>
> > I am trying to configure pacemaker with corosync on RHEL 6.<br>
> ><br>
> > While trying to add lsb resources i get "could not parse meta-data".<br>
> ><br>
> > The pacemaker version is 1.1.7 . Below is the error what i get when i check<br>
> > for metadata in crm shell.<br>
> ><br>
> > *crm(live)ra# list lsb*<br>
> > *abrt-ccpp abrt-oops abrtd<br>
> > acpid atd*<br>
> > *auditd autofs certmonger<br>
> > cgconfig cgred*<br>
> > *corosync corosync-notifyd cpuspeed<br>
> > crond cups*<br>
> > *haldaemon halt heartbeat<br>
> > httpd ip6tables*<br>
> > *iptables irqbalance kdump<br>
> > killall ktune*<br>
> > *lvm2-lvmetad lvm2-monitor matahari-broker<br>
> > matahari-host matahari-network*<br>
> > *matahari-rpc matahari-service matahari-sysconfig<br>
> > matahari-sysconfig-console mcelogd*<br>
> > *mdmonitor messagebus netconsole<br>
> > netfs network*<br>
> > *nfs nfslock ntpd<br>
> > ntpdate oddjobd*<br>
> > *pacemaker portreserve postfix<br>
> > psacct qpidd*<br>
> > *quota_nld rdisc restorecond<br>
> > rhnsd rhsmcertd*<br>
> > *rngd rpcbind rpcgssd<br>
> > rpcidmapd rpcsvcgssd*<br>
> > *rsyslog sandbox saslauthd<br>
> > single smartd*<br>
> > *sshd sssd sysstat<br>
> > tuned udev-post*<br>
> > *ypbind *<br>
> > *crm(live)ra# meta lsb heartbeat*<br>
> > *ERROR: heartbeat:lsb: could not parse meta-data: *<br>
> > *crm(live)ra# meta lsb sshd*<br>
> > *ERROR: sshd:lsb: could not parse meta-data: *<br>
> > *crm(live)ra# meta lsb ntpd*<br>
> > *ERROR: ntpd:lsb: could not parse meta-data: *<br>
> > *crm(live)ra# meta lsb httpd*<br>
> > *ERROR: httpd:lsb: could not parse meta-data*<br>
> ><br>
> > Please do suggest me where am i going wrong.<br>
> > Thanks for the help.<br>
> ><br>
> > Thanks<br>
> > Vishal<br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL: <<br>
> > <a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121022/0ade914c/attachment-0001.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121022/0ade914c/attachment-0001.html</a><br>
> > ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Message: 2<br>
> > Date: Mon, 22 Oct 2012 14:48:31 +0200<br>
> > From: Florian Crouzat <<a href="mailto:gentoo@floriancrouzat.net">gentoo@floriancrouzat.net</a>><br>
> > To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> > Subject: Re: [Pacemaker] lsb: could not parse meta-data<br>
> > Message-ID: <<a href="mailto:5085409F.801@floriancrouzat.net">5085409F.801@floriancrouzat.net</a>><br>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
> ><br>
> > Le 22/10/2012 14:23, vishal kumar a ?crit :<br>
> > > Hi<br>
> ><br>
> > > Please do suggest me where am i going wrong.<br>
> > > Thanks for the help.<br>
> > ><br>
> ><br>
> > See: crm ra help meta<br>
> > Then try something like: crm ra meta sshd lsb # parameters order matter<br>
> ><br>
> > Anyway, you won't learn anything out of meta-datas from a LSB<br>
> > initscript, because it's just a script (not cluster oriented, not a real<br>
> > resource agent), it's not multistate, nothing like that, only<br>
> > start/stop/monitor and default mandatory settings.<br>
> ><br>
> ><br>
> > --<br>
> > Cheers,<br>
> > Florian Crouzat<br>
> ><br>
> ><br>
<br>
> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 23 Oct 2012 16:44:29 +0200<br>
From: Dejan Muhamedagic <<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
Subject: Re: [Pacemaker] Crm configure Error In Centos 5.4<br>
Message-ID: <20121023144428.GA3970@squib><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
On Mon, Oct 15, 2012 at 01:17:47PM +0530, Vinoth Narasimhan wrote:<br>
> Hi Guys,<br>
><br>
> I just installed the latest heartbeat,pacemaker and corosync as per the<br>
> guidelines from the below link<br>
><br>
> <a href="http://www.clusterlabs.org/wiki/Install#READ_ME_FIRST" target="_blank">http://www.clusterlabs.org/wiki/Install#READ_ME_FIRST</a><br>
><br>
> I am able to successfully configure the heartbeat and corosync and start it<br>
> as well.<br>
><br>
> But when i tried to add the resource i am getting the error from python.<br>
><br>
> [root@CHE-PSS-072 lib64]# crm configure<br>
> Traceback (most recent call last):<br>
> File "/usr/sbin/crm", line 41, in ?<br>
> crm.main.run()<br>
> File "/usr/lib64/python2.4/site-packages/crm/main.py", line 240, in run<br>
> parse_line(levels,["configure"])<br>
> File "/usr/lib64/python2.4/site-packages/crm/main.py", line 123, in<br>
> parse_line<br>
> lvl.new_level(pt[token],token)<br>
> File "/usr/lib64/python2.4/site-packages/crm/levels.py", line 70, in<br>
> new_level<br>
> self.current_level = level_obj()<br>
> File "/usr/lib64/python2.4/site-packages/crm/ui.py", line 1295, in<br>
> __init__<br>
> cib_factory.initialize()<br>
> File "/usr/lib64/python2.4/site-packages/crm/cibconfig.py", line 1780, in<br>
> initialize<br>
> if not self.import_cib():<br>
> File "/usr/lib64/python2.4/site-packages/crm/cibconfig.py", line 1454, in<br>
> import_cib<br>
> self.doc,cib = read_cib(cibdump2doc)<br>
> File "/usr/lib64/python2.4/site-packages/crm/xmlutil.py", line 72, in<br>
> read_cib<br>
> doc = fun(params)<br>
> File "/usr/lib64/python2.4/site-packages/crm/xmlutil.py", line 53, in<br>
> cibdump2doc<br>
> doc = xmlparse(p.stdout)<br>
> File "/usr/lib64/python2.4/site-packages/crm/xmlutil.py", line 30, in<br>
> xmlparse<br>
> except xml.parsers.expat.ExpatError,msg:<br>
> AttributeError: 'module' object has no attribute 'expat'<br>
<br>
Hmm, the official python documentation<br>
(<a href="http://docs.python.org/library/pyexpat.html" target="_blank">http://docs.python.org/library/pyexpat.html</a>) states that expat<br>
is "New in version 2.0". Can you check your python installation.<br>
AFAIK, crmsh is being used on various EL5.<br>
<br>
Thanks,<br>
<br>
Dejan<br>
<br>
> However i am get the status correctly.<br>
><br>
> [root@CHE-PSS-072 lib64]# crm status<br>
> ============<br>
> Last updated: Mon Oct 15 00:46:53 2012<br>
> Stack: Heartbeat<br>
> Current DC: <a href="http://che-pss-072.ps.in" target="_blank">che-pss-072.ps.in</a> (dd4d1fd0-97ff-4a28-aac2-302ee1066e4c) -<br>
> partition with quorum<br>
> Version: 1.0.12-unknown<br>
> 2 Nodes configured, unknown expected votes<br>
> 0 Resources configured.<br>
> ============<br>
><br>
> Online: [ <a href="http://che-pss-072.ps.in" target="_blank">che-pss-072.ps.in</a> <a href="http://ops-pss-084.ps.in" target="_blank">ops-pss-084.ps.in</a> ]<br>
><br>
> Any help is greatly appreciated to solve the error.<br>
><br>
> Thanks,<br>
> vinoth.<br>
<br>
> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 23 Oct 2012 16:46:14 +0200<br>
From: Dejan Muhamedagic <<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
Subject: Re: [Pacemaker] external/ssh stonith and repeated reboots<br>
Message-ID: <20121023144614.GB3970@squib><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Hi,<br>
<br>
On Tue, Oct 16, 2012 at 03:00:08PM +1100, Andrew Beekhof wrote:<br>
> On Sun, Oct 14, 2012 at 5:04 PM, James Harper<br>
> <<a href="mailto:james.harper@bendigoit.com.au">james.harper@bendigoit.com.au</a>> wrote:<br>
> > I'm using external/ssh in my test cluster (a bunch of vm's), and for some reason the cluster has tried to terminate it but failed, like:<br>
><br>
> Try fence_xvm instead. Its actually reliable.<br>
> You'd need the fence-virtd on the host and guests package and I've had<br>
> plenty of success with the following as the config file on the host.<br>
> Make sure key_file exists everywhere, start fence-virtd and test with<br>
> "fence_xvm -o list" on the guest(s)<br>
<br>
There's also external/libvirt which should do fine.<br>
<br>
> ssh based fencing isn't just "not for production" its a flat out terrible idea.<br>
> With much handwaving it is barely usable even for testing as it<br>
> requires the target to be alive, reachable and behaving.<br>
<br>
Indeed.<br>
<br>
Thanks,<br>
<br>
Dejan<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 23 Oct 2012 10:04:31 -0500 (CDT)<br>
From: Andrew Martin <<a href="mailto:amartin@xes-inc.com">amartin@xes-inc.com</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
Subject: Re: [Pacemaker] Behavior of Corosync+Pacemaker with DRBD<br>
primary power loss<br>
Message-ID: <5651a700-b509-40ec-8d79-49b77e53c30e@zimbra><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hello,<br>
<br>
Under the Clusters from Scratch documentation, allow-two-primaries is set in the DRBD configuration for an active/passive cluster:<br>
<a href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html-single/Clusters_from_Scratch/index.html#_write_the_drbd_config" target="_blank">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html-single/Clusters_from_Scratch/index.html#_write_the_drbd_config</a><br>
<br>
"TODO: Explain the reason for the allow-two-primaries option"<br>
<br>
Is the reason for allow-two-primaries in this active/passive cluster (using ext4, a non-cluster filesystem) to allow for failover in the type of situation I have described (where the old primary/master is suddenly offline like with a power supply failure)? Are split-brains prevented because Pacemaker ensures that only one node is promoted to Primary at any time?<br>
<br>
Is it possible to recover from such a failure without allow-two-primaries?<br>
<br>
Thanks,<br>
<br>
Andrew<br>
<br>
----- Original Message -----<br>
<br>
From: "Andrew Martin" <<a href="mailto:amartin@xes-inc.com">amartin@xes-inc.com</a>><br>
To: "The Pacemaker cluster resource manager" <<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
Sent: Friday, October 19, 2012 10:45:04 AM<br>
Subject: [Pacemaker] Behavior of Corosync+Pacemaker with DRBD primary power loss<br>
<br>
<br>
Hello,<br>
<br>
I have a 3 node Pacemaker + Corosync cluster with 2 "real" nodes, node0 and node1, running a DRBD resource (single-primary) and the 3rd node in standby acting as a quorum node. If node0 were running the DRBD resource, and thus is DRBD primary, and its power supply fails, will the DRBD resource be promoted to primary on node1?<br>
<br>
If I simply cut the DRBD replication link, node1 reports the following state:<br>
Role:<br>
Secondary/Unknown<br>
<br>
Disk State:<br>
UpToDate/DUnknown<br>
<br>
Connection State:<br>
WFConnection<br>
<br>
<br>
I cannot manually promote the DRBD resource because the peer is not outdated:<br>
0: State change failed: (-7) Refusing to be Primary while peer is not outdated<br>
Command 'drbdsetup 0 primary' terminated with exit code 11<br>
<br>
I have configured the CIB-based crm-fence-peer.sh utility in my drbd.conf<br>
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";<br>
but I do not believe it would be applicable in this scenario.<br>
<br>
If node0 goes offline like this and doesn't come back (e.g. after a STONITH), does Pacemaker have a way to tell node1 that its peer is outdated and to proceed with promoting the resource to primary?<br>
<br>
Thanks,<br>
<br>
Andrew<br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121023/dfe33346/attachment-0001.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121023/dfe33346/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 23 Oct 2012 10:29:44 -0500<br>
From: Justin Pasher <<a href="mailto:justinp@distribion.com">justinp@distribion.com</a>><br>
To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
Subject: Re: [Pacemaker] "Simple" LVM/drbd backed Primary/Secondary<br>
NFS cluster doesn't always failover cleanly<br>
Message-ID: <<a href="mailto:5086B7E8.7010900@distribion.com">5086B7E8.7010900@distribion.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
----- Original Message -----<br>
> From: Andreas Kurz <<a href="mailto:andreas@hastexo.com">andreas@hastexo.com</a>><br>
> Date: Sun, 21 Oct 2012 01:38:46 +0200<br>
> Subject: Re: [Pacemaker] "Simple" LVM/drbd backed Primary/Secondary<br>
NFS cluster doesn't always failover cleanly<br>
> To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
><br>
><br>
> On 10/18/2012 08:02 PM, Justin Pasher wrote:<br>
>> I have a pretty basic setup by most people's standards, but there must<br>
>> be something that is not quite right about it. Sometimes when I force a<br>
>> resource failover from one server to the other, the clients with the NFS<br>
>> mounts don't cleanly migrate to the new server. I configured this using<br>
>> a few different "Pacemaker-DRBD-NFS" guides out there for reference (I<br>
>> believe they were the Linbit guides).<br>
> Are you using the latest "exportfs" resource-agent from github-repo? ...<br>
> there have been bugfixes/improvements... and try to move the VIP for<br>
> each export to the end of its group so the IP where the clients connect<br>
> is started at the last/stopped at the first position.<br>
><br>
> Regards,<br>
> Andreas<br>
<br>
I'm current running the version that comes with the Debian<br>
squeeze-backports resource-agents package (1:3.9.2-5~bpo60+1). I went<br>
ahead and grabbed a copy of exportfs from the git repository. It's a<br>
little risky for me to update the file right now, since the two<br>
resources I am worried about the most are the NFS shares for the<br>
XenServer VDIs, so when it has a hiccup in the connection to the NFS<br>
server, things start exploding (e.g. guest VMs start having disk errors<br>
and go read-only).<br>
<br>
I scanned through the changes real quick and the biggest change I<br>
noticed was how the .rmtab file backup is restored (it sorts and filters<br>
unique entries instead of just concatenating the results to the end of<br>
/var/lib/nfs/rmtab). I had actually tweaked that a little bit myself<br>
before when I was trying to trace down the problem.<br>
<br>
Ultimately I think my problem is more related to the NFS server itself<br>
and how it handles "unknown" client connections after a failover. I've<br>
see people here and there mention that /var/lib/nfs should be on the<br>
replicated device to maintain consistency after fail over, but the<br>
exportfs resource agent doesn't do anything like that. Is that not<br>
actually needed anymore? At any rate, in my situation, the problem is<br>
that I am maintaining four independent NFS shares and each one can be<br>
failed over separately (and running on either server at any time), so a<br>
simple copy of the directory won't work since there is no "master"<br>
server at any given time.<br>
<br>
Also, I did find a bug in the way backup_rmtab() filters the export list<br>
for its backup. Since it looks for a leading AND trailing colon (:), it<br>
doesn't properly copy information about mounts that pulled from<br>
subdirectories under the NFS mount (e.g. instead of mounting /home, a<br>
server might mount /home/username such as with autofs, which won't get<br>
copied to the .rmtab backup). I'll file a bug report about that.<br>
<br>
Thanks.<br>
<br>
--<br>
Justin Pasher<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 23 Oct 2012 10:50:11 -0500<br>
From: Cal Heldenbrand <<a href="mailto:cal@fbsdata.com">cal@fbsdata.com</a>><br>
To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
Subject: [Pacemaker] crm_simulate a resource failure<br>
Message-ID:<br>
<<a href="mailto:CAAcwKhf6iLv9q9H3BgTSQ5scLPpuDmUeZ1fLWhYf09nRwRjn2g@mail.gmail.com">CAAcwKhf6iLv9q9H3BgTSQ5scLPpuDmUeZ1fLWhYf09nRwRjn2g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi everyone,<br>
<br>
I'm not able to find documentation or examples on this. If I have a cloned<br>
primitive set across a cluster, how can I simulate a failure of a resource<br>
on an individual node? I mainly want to see the scores on why a particular<br>
action is taken so I can adjust my configs.<br>
<br>
I think the --op-fail parameter is what I need, but I just don't get the<br>
syntax of the value in the man page.<br>
<br>
Thank you!<br>
<br>
--Cal<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121023/1c3630c3/attachment.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20121023/1c3630c3/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
<br>
End of Pacemaker Digest, Vol 59, Issue 59<br>
*****************************************<br>
</blockquote></div><br>