<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'>Hello,<div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">My setup:</span><div> I have a 2 node cluster using pacemaker and heartbeat. I have 2 resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server. </div><div> I have these 2 resources grouped together and they will fail over to the other node.</div></div><div><br></div><div><br></div><div><br></div><div>question:</div><div> When rabbitmq is migrated to node1 from node2 I would like to 'not' have the the </etc/init.d/rabbitmq-server stop> happen on the failed server (node1 in this example).</div><div><br></div><div> Is it possible to do this in crm? </div><div> </div><div> I realize that I could hack the initscript's case statement for stop to just "exit 0", but I am hoping there is a way to do this in crm.</div><div><br></div><div> </div><div>Thanks for any help,</div><div>Steve</div><div> </div><div><br></div> </div></body>
</html>