Sorry I neglected to mention that the main reason I need/want to 'reload' the services is to ensure that they start listening on the newly acquired virtual IP.<br><br><br><div class="gmail_quote">On Tue, Nov 3, 2009 at 8:30 PM, bards 1888 <span dir="ltr"><<a href="mailto:bards1888@gmail.com">bards1888@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I have been playing with pacemaker and openais to try and get some sort of high-availability for the following services;<br>
<br>1. named<br>2. squid<br>3. dansguardian<br><br><br>My basic requirements are, a floating virtual IP that can exist on either node of my 2 node cluster. Users will have a single server setup for DNS and proxy and that will be the virtual IP. Obviously, the users will then get directed to the 'master' node and all will be well. However, I want to be able to run the services on the second node at the same time, so that, for example, I can point my browser at the second proxy or have the slave DNS server updated as zone changes are made on the master.<br>
<br>Is there any way I can define just the IP address as the Resource agent and say "if you get the virtual IP, run this script" which would effectively run /etc/init.d/service reload for each of the three services ?<br>
<br>Any help/advice would be appreciated.<br><br>Cheers<br>
</blockquote></div><br>