<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Thanks, that is very helpful information. Looks like I need to modify the init script.<br><br>-Andrew L<br><br><hr id="zwchr"><b>From: </b>"Michael Hittesdorf" <michael.hittesdorf@chicagotrading.com><br><b>To: </b>"The Pacemaker cluster resource manager" <pacemaker@oss.clusterlabs.org><br><b>Sent: </b>Thursday, January 6, 2011 12:54:10 PM<br><b>Subject: </b>Re: [Pacemaker] Resource monitoring actions when a resource diesuncleanly<br><br>
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:navy;
text-decoration:underline;}
p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Your init script needs to be LSB
compliant. See this link for details <a href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html" target="_blank">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html</a>.
Basically, in the case of stop, it always needs to return 0. You can change
the squid init script or write an lsb compliant wrapper init script that calls
the squid init script. Hope this helps.</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;">Mick</span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;"> </span></font></p>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr width="100%" align="center" size="2">
</span></font></div>
<p class="MsoNormal"><b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font face="Tahoma" size="2"><span style="font-size: 10pt; font-family: Tahoma;"> Andrew Lacey
[mailto:alacey@brynmawr.edu] <br>
<b><strong>Sent:</strong></b> Thursday, January 06, 2011
11:41 AM<br>
<b><span style="font-weight: bold;">To:</span></b> pacemaker@oss.clusterlabs.org<br>
<b><span style="font-weight: bold;">Subject:</span></b> [Pacemaker] Resource
monitoring actions when a resource diesuncleanly</span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size: 12pt;"> </span></font></p>
<div>
<p class="MsoNormal"><font color="black" face="Times New Roman" size="3"><span style="font-size: 12pt; color: black;">Hi-<br>
<br>
First off, I'm new to Pacemaker and there's a tremendous amount of information
to sift through, so my apologies if this has been answered already.<br>
<br>
I'm trying to set up a simple 2-node active/passive cluster that runs squid
(reverse proxy for web services) on a service IP address. I'm not using STONITH
because there's no shared data, so nothing horrible would happen if squid
somehow ends up running on both boxes. So, there are just two resources, squid
itself and the IP address, configured as a resource group because they must be
on the same machine.<br>
<br>
I've done some investigation on setting up resource monitoring for squid.
Ideally, if squid dies for any reason on the currently-active node, I would
like to fail both resources (squid and IP) over to the other node. For resource
monitoring, there is an on-fail action called "standby", which is
described as: "Move <em><i><font face="Times New Roman">all</font></i></em>
resources away from the node on which the resource failed." That sounded
to me like what I want, so I tested it. Unfortunately, I found that if squid
dies uncleanly (simulated by issuing a kill -9 to its process), Pacemaker gets
into an infinite loop of repeatedly trying to use the init script to
"stop" squid. The init script is returning some error value because,
in its words, "squid is dead but pid file exists". squid is never started
on the other node because Pacemaker is never satisfied that it has truly
stopped on the original node.<br>
<br>
Since a typical unexpected software failure would be an unclean failure (seg
fault or whatever), this monitoring doesn't seem very useful if it always gets
stuck trying to "stop" the crashed service before taking any further
action. Is there a generally-accepted way around this? Should the init script
(LSB) be rewritten to respond differently to this situation, or is there some
way to get Pacemaker to respond differently?<br>
<br>
Thanks,<br>
<br>
-Andrew L</span></font></p>
</div>
</div>
<p></p><p><font size="1">This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.</font><font size="1"> If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.</font><font size="1"> Neither CTC Holdings nor any affiliates (CTC) are responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity that may be attached to or contained in this communication. CTC accepts no liability for any content contained in the email, or any errors or omissions arising as a result of e-mail transmission.</font><font size="1"> Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. CTC London Limited is authorized and regulated by the Financial Services Authority.</font></p><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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker<br></div></body></html>