<p>Here: <a href="https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/named">https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/named</a></p>
<p>Let me know how it works for you.</p>
<div class="gmail_quote">On Sep 29, 2011 8:25 AM, "Max Williams" <<a href="mailto:Max.Williams@betfair.com">Max.Williams@betfair.com</a>> wrote:<br type="attribution">> Yes I was using the LSB RA. Can you give me a link to the OCF RA on github?<br>
> Thanks,<br>> Max<br>> <br>> From: Serge Dubrouski [mailto:<a href="mailto:sergeyfd@gmail.com">sergeyfd@gmail.com</a>]<br>> Sent: 29 September 2011 13:19<br>> To: The Pacemaker cluster resource manager<br>
> Subject: Re: [Pacemaker] Reloading a resource after a failover<br>> <br>> What kind of RA you do you use? LSB one doesn't support reload, OCF - does. You need to get OCF RA from github,.<br>> On Thu, Sep 29, 2011 at 3:04 AM, Max Williams <<a href="mailto:Max.Williams@betfair.com">Max.Williams@betfair.com</a><mailto:<a href="mailto:Max.Williams@betfair.com">Max.Williams@betfair.com</a>>> wrote:<br>
> Yes this is what I would like to do. Ideally have named as a clone and then have an order like this:<br>> crm(live)configure# order named-service-clone-after-Cluster_IP inf: Cluster_IP:start Named_Service:reload<br>
> But it gives this error:<br>> ERROR: bad resource action/instance definition: Named_Service:reload<br>> <br>> Is there a way to achieve this?<br>> Can I edit an RA file so that it takes reload as a action? If so, which file?<br>
> Or configure pacemaker to run an external command when a resource fails over or moves?<br>> <br>> Many thanks,<br>> Max<br>> <br>> From: Serge Dubrouski [mailto:<a href="mailto:sergeyfd@gmail.com">sergeyfd@gmail.com</a><mailto:<a href="mailto:sergeyfd@gmail.com">sergeyfd@gmail.com</a>>]<br>
> Sent: 28 September 2011 18:17<br>> To: The Pacemaker cluster resource manager<br>> Subject: Re: [Pacemaker] Reloading a resource after a failover<br>> <br>> <br>> Put bind itself under pacemaker control. You can use LSB RA or OCF RA that I recently created.<br>
> On Sep 28, 2011 10:46 AM, "Max Williams" <<a href="mailto:Max.Williams@betfair.com">Max.Williams@betfair.com</a><mailto:<a href="mailto:Max.Williams@betfair.com">Max.Williams@betfair.com</a>>> wrote:<br>
>> Hi,<br>>> I have a pair of clustered DNS servers with a virtual IP (VIP) configured. The problem is that when the VIP fails over, named on the new host of the VIP will not listen on port 53/UDP of the VIP until it is reloaded (I think this is because this daemon uses UDP, not TCP).<br>
>><br>>> So I'd like to be able to reload named after a failover of the VIP address. Is this possible?<br>>><br>>> I could do it by configuring named as a cloned resource and then configuring an order so that it is restarted when the VIP fails over or moves but I would much rather have named reload instead of restart.<br>
>><br>>> Any ideas? I'd rather not have to resort to a wrapper script or anything like that.<br>>><br>>> Thanks,<br>>> Max<br>>><br>>> ________________________________________________________________________<br>
>> In order to protect our email recipients, Betfair Group use SkyScan from<br>>> MessageLabs to scan all Incoming and Outgoing mail for viruses.<br>>><br>>> ________________________________________________________________________<br>
>><br>>> _______________________________________________<br>>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>><br>
>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>>><br>>> Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a><br>
>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>>> Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
> <br>> ________________________________________________________________________<br>> In order to protect our email recipients, Betfair Group use SkyScan from<br>> MessageLabs to scan all Incoming and Outgoing mail for viruses.<br>
> <br>> ________________________________________________________________________<br>> <br>> _______________________________________________<br>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><mailto:<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>> <br>> Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
> <br>> <br>> <br>> --<br>> Serge Dubrouski.<br>> <br>> ________________________________________________________________________<br>> In order to protect our email recipients, Betfair Group use SkyScan from <br>
> MessageLabs to scan all Incoming and Outgoing mail for viruses.<br>> <br>> ________________________________________________________________________<br></div>