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.willi...@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:serge...@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.willi...@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@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@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.
_______________________________________________ Pacemaker mailing list: Pacemaker@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