<div dir="ltr">This isn't related to your problem, but i seen this in your cluster config primitive cluster-ntp lsb:ntp, i don't think is a good idea to have a ntp in failover(local service), in a cluster the time needs to be synchronized on all nodes<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-22 9:31 GMT+02:00 Danilo Malcangio <span dir="ltr"><<a href="mailto:d.malcangio@eletech.it" target="_blank">d.malcangio@eletech.it</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi everyone,<br>
I've created an active/passive 2 node cluster following the
documentation on clusterlabs.<br>
My cluster has the following characteristics<br>
Debian Wheezy 7.2.0<br>
Pacemaker 1.1.7<br>
Corosync 1.4.2<br>
<br>
I've made it with the following configuration<br>
<br>
node BX-1<br>
node BX-2<br>
primitive cluster-apache2 ocf:heartbeat:apache \<br>
params configfile="/etc/apache2/apache2.conf"
httpd="/usr/sbin/apache2" port="80" \<br>
op monitor interval="10s" timeout="60s" \<br>
op start interval="0" timeout="40s" \<br>
op stop interval="0" timeout="60s"<br>
primitive cluster-asterisk lsb:asterisk \<br>
op monitor interval="30" \<br>
op start interval="0" timeout="120s" \<br>
op stop interval="0" timeout="120s"<br>
primitive cluster-ip ocf:heartbeat:IPaddr2 \<br>
params ip="10.2.30.10" cidr_netmask="20" \<br>
op monitor interval="10s" timeout="20s" \<br>
op start interval="0" timeout="20s" \<br>
op stop interval="0" timeout="20s"<br>
primitive cluster-ntp lsb:ntp \<br>
op monitor interval="30" \<br>
op start interval="0" timeout="120s" \<br>
op stop interval="0" timeout="120s"<br>
primitive cluster-tftp lsb:tftpd-hpa \<br>
op monitor interval="30" \<br>
op start interval="0" timeout="120s" \<br>
op stop interval="0" timeout="120s"<br>
group cluster-group cluster-ip cluster-asterisk cluster-apache2
cluster-tftp cluster-ntp \<br>
meta resource-stickiness="101"<br>
location prefer-et-ipbx-1 cluster-group 100: BX-1<br>
colocation cluster-dependency inf: cluster-ip cluster-asterisk
cluster-apache2 cluster-tftp cluster-ntp<br>
property $id="cib-bootstrap-options" \<br>
dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \<br>
cluster-infrastructure="openais" \<br>
expected-quorum-votes="2" \<br>
stonith-enabled="false" \<br>
no-quorum-policy="ignore" \<br>
default-resource-stickiness="1"<br>
rsc_defaults $id="rsc-options" \<br>
failure-timeout="60s"<br>
<br>
I've set location constraint to have BX-1 as the preferred node at
cluster startup, and group stickiness at 101 to avoid moving
resources when the master node comes back up (following this guide
<a href="http://foaa.de/old-blog/2010/10/intro-to-pacemaker-part-2-advanced-topics/trackback/index.html" target="_blank">http://foaa.de/old-blog/2010/10/intro-to-pacemaker-part-2-advanced-topics/trackback/index.html</a>).<br>
<br>
I've got the following problem: resources move when I reboot nodes.<br>
<br>
If i stop corosync on BX-1 resources move to BX-2 and when i restart
corosync on BX-1 they stay on BX-2 (as I expected). <br>
But all this doesn't happen with reboot (when I reboot BX-1).<br>
After the reboot of BX-1 resources move to BX-2 and when BX-1 comes
back up the resources move back to BX-1.<br>
<br>
What am I missing in the configuration??<br>
<br>
Thank you very much for the support<br>
<br>
<br>
<br>
P.s. I attach also the allocation scores obtained with ptest -sL<br>
<br>
BX-1 has resources<br>
<br>
Allocation scores:<br>
group_color: et-cluster allocation score on ET-IPBX-1: 100<br>
group_color: et-cluster allocation score on ET-IPBX-2: 0<br>
group_color: cluster-ip allocation score on ET-IPBX-1: 201<br>
group_color: cluster-ip allocation score on ET-IPBX-2: 0<br>
group_color: cluster-asterisk allocation score on ET-IPBX-1: 101<br>
group_color: cluster-asterisk allocation score on ET-IPBX-2: 0<br>
group_color: cluster-apache2 allocation score on ET-IPBX-1: 101<br>
group_color: cluster-apache2 allocation score on ET-IPBX-2: 0<br>
group_color: cluster-tftp allocation score on ET-IPBX-1: 101<br>
group_color: cluster-tftp allocation score on ET-IPBX-2: 0<br>
group_color: cluster-ntp allocation score on ET-IPBX-1: 101<br>
group_color: cluster-ntp allocation score on ET-IPBX-2: 0<br>
native_color: cluster-ip allocation score on ET-IPBX-1: 3231<br>
native_color: cluster-ip allocation score on ET-IPBX-2: 0<br>
native_color: cluster-asterisk allocation score on ET-IPBX-1: 1515<br>
native_color: cluster-asterisk allocation score on ET-IPBX-2:
-INFINITY<br>
native_color: cluster-apache2 allocation score on ET-IPBX-1: 707<br>
native_color: cluster-apache2 allocation score on ET-IPBX-2:
-INFINITY<br>
native_color: cluster-tftp allocation score on ET-IPBX-1: 303<br>
native_color: cluster-tftp allocation score on ET-IPBX-2: -INFINITY<br>
native_color: cluster-ntp allocation score on ET-IPBX-1: 101<br>
native_color: cluster-ntp allocation score on ET-IPBX-2: -INFINITY<br>
<br>
BX-2 has resources (while BX-1 reboot)<br>
<br>
Allocation scores:<br>
group_color: et-cluster allocation score on ET-IPBX-1: -INFINITY<br>
group_color: et-cluster allocation score on ET-IPBX-2: 0<br>
group_color: cluster-ip allocation score on ET-IPBX-1: -INFINITY<br>
group_color: cluster-ip allocation score on ET-IPBX-2: 101<br>
group_color: cluster-asterisk allocation score on ET-IPBX-1: 0<br>
group_color: cluster-asterisk allocation score on ET-IPBX-2: 101<br>
group_color: cluster-apache2 allocation score on ET-IPBX-1: 0<br>
group_color: cluster-apache2 allocation score on ET-IPBX-2: 101<br>
group_color: cluster-tftp allocation score on ET-IPBX-1: 0<br>
group_color: cluster-tftp allocation score on ET-IPBX-2: 101<br>
group_color: cluster-ntp allocation score on ET-IPBX-1: 0<br>
group_color: cluster-ntp allocation score on ET-IPBX-2: 101<br>
native_color: cluster-ip allocation score on ET-IPBX-1: -INFINITY<br>
native_color: cluster-ip allocation score on ET-IPBX-2: 3131<br>
native_color: cluster-asterisk allocation score on ET-IPBX-1:
-INFINITY<br>
native_color: cluster-asterisk allocation score on ET-IPBX-2: 1515<br>
native_color: cluster-apache2 allocation score on ET-IPBX-1:
-INFINITY<br>
native_color: cluster-apache2 allocation score on ET-IPBX-2: 707<br>
native_color: cluster-tftp allocation score on ET-IPBX-1: -INFINITY<br>
native_color: cluster-tftp allocation score on ET-IPBX-2: 303<br>
native_color: cluster-ntp allocation score on ET-IPBX-1: -INFINITY<br>
native_color: cluster-ntp allocation score on ET-IPBX-2: 101
<div>
<hr align="left" color="#000080" size="1" width="282"> </div>
</div>
<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://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>esta es mi vida e me la vivo hasta que dios quiera
</div>