If you want to make your LDAP independent from IP just remove your collocation:<br><br>colocation ldap-with-eip inf: elastic_ip ldap-clone<br><br>But I'd rather try to find out why monitoring for IP fails. May bet it just needs an increased timeout on monitor operation, though it looks like you've already increased it. What's in your log files when that monitor fails?<br>
<br><div class="gmail_quote">On Mon, Jun 27, 2011 at 9:39 AM, veghead <span dir="ltr"><<a href="mailto:sean@studyblue.com">sean@studyblue.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
veghead <sean@...> writes:<br>
> Pair of LDAP servers running 389 (formerly Fedora DS) in<br>
> high availability using Pacemaker with a floating IP.<br>
> In addition, 389 supports multi-master replication,<br>
> where all changes on one node are automatically<br>
> replicated on one or more other nodes.<br>
<br>
I'm so close, but I'm still having issues. I'm running these on EC2 using an<br>
ElasticIP as the "floating" ip. Unfortunately, I have found that requests for<br>
the status of the ElasticIP occasionally fail for no apparent reason, even<br>
thought he ElasticIP is actually working fine. Once they fail, that triggers a<br>
failover and creates a mess.<br>
<br>
What I'd like to do is:<br>
<br>
* Run LDAP service on both nodes<br>
* Ignore the status of the ElasticIP resource and only trigger a fail-over when<br>
the LDAP service fails.<br>
<br>
I feel like my config is close, but the cluster keeps wanting to stop the<br>
resources.<br>
<br>
Here's my current config:<br>
<br>
---snip---<br>
primitive elastic_ip lsb:elastic-ip \<br>
op monitor interval="0" timeout="300" on-fail="ignore"<br>
requires="nothing"<br>
primitive ldap lsb:dirsrv \<br>
op monitor interval="15s" on-fail="standby" requires="nothing"<br>
clone ldap-clone ldap<br>
colocation ldap-with-eip inf: elastic_ip ldap-clone<br>
order ldap-after-eip inf: elastic_ip ldap-clone<br>
property $id="cib-bootstrap-options" \<br>
dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \<br>
cluster-infrastructure="Heartbeat" \<br>
stonith-enabled="false" \<br>
no-quorum-policy="ignore" \<br>
stop-all-resources="true"<br>
rsc_defaults $id="rsc-options" \<br>
resource-stickiness="100"<br>
---snip---<br>
<br>
Any suggestions as to what I'm doing wrong?<br>
<br>
<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" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Serge Dubrouski.<br>