<p>OCF script for bind was recently added to cluster-resources on gorging. Could you please try to use that one?</p>
<div class="gmail_quote">On Sep 30, 2011 2:09 AM, "Gerald Vogt" <<a href="mailto:vogt@spamcop.net">vogt@spamcop.net</a>> wrote:<br type="attribution">> Hi!<br>> <br>> I am running a cluster with 3 nodes. These nodes provide dns service.<br>
> The purpose of the cluster is to have our two dns service ip addresses<br>> online at all times. I use IPaddr2 and that part works.<br>> <br>> Now I try to extend our setup to check the dns service itself. So far,<br>
> if a dns server on any node stops or hangs the cluster won't notice.<br>> Thus, I wrote a custom ocf script to check whether the dns service on<br>> a node is operational (i.e. if the dns server is listening on the ip<br>
> address and whether it responds to a dns request).<br>> <br>> All cluster nodes are slave dns servers, therefore the dns server<br>> process is running at all times to get zone transfers from the dns<br>> master.<br>
> <br>> Obviously, the dns service resource must be colocated with the IP<br>> address resource. However, as the dns server is running at all times,<br>> the dns service resource must be started or stopped after the ip<br>
> address. This leads me to something like this:<br>> <br>> primitive ns1-ip ocf:heartbeat:IPaddr2 ...<br>> primitive ns1-dns ocf:custom:dns op monitor interval="30s"<br>> <br>> colocation dns-ip1 inf: ns1-dns ns1-ip<br>
> order ns1-ip-dns inf: ns1-ip ns1-dns symmetrical=false<br>> <br>> Problem 1: it seems as if the order constraint does not wait for an<br>> operation on the first resource to finish before it starts the<br>> operation on the second. When I migrate an IP address to another node<br>
> the stop operation on ns1-dns will fail because the ip address is<br>> still active on the network interface. I have worked around this by<br>> checking for the IP address on the interface in the stop part of my<br>
> dns script and sleeping 5 seconds if it is still there before checking<br>> again and continuing.<br>> <br>> Shouldn't the stop on ns1-ip first finish before the node initiates<br>> the stop on ns1-dns?<br>
> <br>> Problem 2: if the dns service fails, e.g. hangs, the monitor operation<br>> fails. Thus, the cluster wants to migrate the ip address and service<br>> to another node. However, it first initiates a stop on ns1-dns and<br>
> then on ns1-ip.<br>> <br>> What I need is ns1-ip to stop before ns1-dns. But this seems<br>> impossible to configure. The order constraint only says what operation<br>> is executed on ns1-dns depending on the status of ns1-ip. It says what<br>
> happens after something. It cannot say what happens before something.<br>> Is that correct? Or am I missing a configuration option?<br>> <br>> Thanks,<br>> <br>> Gerald<br>> <br>> _______________________________________________<br>
> Pacemaker mailing list: <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></div>