[Pacemaker] Reloading a resource after a failover

[Max Williams]

Thanks Serge.

How exactly do I tell pacemaker to use this RA? Is there an 'import' command I need to run?

Also, does this mean I need to change some of the paths in the RA?

[root at host001 ~]# ocf-tester -n named /usr/lib/ocf/resource.d/heartbeat/named
Beginning tests for /usr/lib/ocf/resource.d/heartbeat/named...
/usr/lib/ocf/resource.d/heartbeat/named: line 16: /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs: No such file or directory
* rc=1: Your agent has too restrictive permissions: should be 755
/usr/lib/ocf/resource.d/heartbeat/named: line 16: /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs: No such file or directory
* rc=127: Your agent was active and could not be stopped
Aborting tests

Cheers,
Max

From: Serge Dubrouski [mailto:sergeyfd at gmail.com]
Sent: 29 September 2011 16:24
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Reloading a resource after a failover


Here: https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/named

Let me know how it works for you.
On Sep 29, 2011 8:25 AM, "Max Williams" <Max.Williams at betfair.com<mailto:Max.Williams at betfair.com>> wrote:
> Yes I was using the LSB RA. Can you give me a link to the OCF RA on github?
> Thanks,
> Max
>
> From: Serge Dubrouski [mailto:sergeyfd at gmail.com<mailto:sergeyfd at gmail.com>]
> Sent: 29 September 2011 13:19
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Reloading a resource after a failover
>
> What kind of RA you do you use? LSB one doesn't support reload, OCF - does. You need to get OCF RA from github,.
> On Thu, Sep 29, 2011 at 3:04 AM, Max Williams <Max.Williams at betfair.com<mailto:Max.Williams at betfair.com><mailto:Max.Williams at betfair.com<mailto:Max.Williams at betfair.com>>> wrote:
> Yes this is what I would like to do. Ideally have named as a clone and then have an order like this:
> crm(live)configure# order named-service-clone-after-Cluster_IP inf: Cluster_IP:start Named_Service:reload
> But it gives this error:
> ERROR: bad resource action/instance definition: Named_Service:reload
>
> Is there a way to achieve this?
> Can I edit an RA file so that it takes reload as a action? If so, which file?
> Or configure pacemaker to run an external command when a resource fails over or moves?
>
> Many thanks,
> Max
>
> From: Serge Dubrouski [mailto:sergeyfd at gmail.com<mailto:sergeyfd at gmail.com><mailto:sergeyfd at gmail.com<mailto:sergeyfd at gmail.com>>]
> Sent: 28 September 2011 18:17
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Reloading a resource after a failover
>
>
> Put bind itself under pacemaker control. You can use LSB RA or OCF RA that I recently created.
> On Sep 28, 2011 10:46 AM, "Max Williams" <Max.Williams at betfair.com<mailto:Max.Williams at betfair.com><mailto:Max.Williams at betfair.com<mailto:Max.Williams at betfair.com>>> wrote:
>> Hi,
>> 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).
>>
>> So I'd like to be able to reload named after a failover of the VIP address. Is this possible?
>>
>> 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.
>>
>> Any ideas? I'd rather not have to resort to a wrapper script or anything like that.
>>
>> Thanks,
>> Max
>>
>> ________________________________________________________________________
>> In order to protect our email recipients, Betfair Group use SkyScan from
>> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>>
>> ________________________________________________________________________
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org><mailto:Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>>
>> http://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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
> ________________________________________________________________________
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
> ________________________________________________________________________
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org><mailto:Pacemaker at oss.clusterlabs.org<mailto:Pacemaker at oss.clusterlabs.org>>
> http://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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>
>
> --
> Serge Dubrouski.
>
> ________________________________________________________________________
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
> ________________________________________________________________________

________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from 
MessageLabs to scan all Incoming and Outgoing mail for viruses.

________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111004/ee2a114b/attachment-0003.html>