[Pacemaker] new in list - corosync failover problem

[Brett Delle Grazie]

Hello,

On Mon, 2010-08-16 at 17:27 +0200, Andreas Kurz wrote:
> hello,
> 
> On 2010-08-16 04:30, Emanuel dos Reis Rodrigues wrote:
> > hello all,
> >
> > I has beens installed a pacemaker with corosync cluster with 2 nodes,
> > and one resource to ip failover follow instructions from:
> > http://clusterlabs.org/wiki/Debian_Lenny_HowTo
> >
> >
> > When I put the node01 in stanby, the services go to node02, but if I
> > stop corosync the resources stop too ...
> >
> > I thing in the quorum problem, because has two nodes ... then I config
> > to ignore quorum policy and nothing ...
> >
> > I add third node and continue .. the same problem ... the service not
> > failover.
> >
> > follow my configuration:
> >
> >
> > debian01:~# crm configure show
> > node debian01 \
> > attributes standby="off"
> > node debian02 \
> > attributes standby="off"
> > node debian03
> > primitive failover-ip ocf:heartbeat:IPaddr \
> > params ip="192.168.188.100" \
> > op monitor interval="10s" \
> > meta target-role="Started"
> > location cli-prefer-failover-ip failover-ip \
> > rule $id="cli-prefer-rule-failover-ip" inf: #uname eq debian01
Also try:
location cli-prefer-failover-ip failover-ip 100: debian01
in addition to symmetric-cluster="true"

inf means always start the IP on that node - so much so that it may not
be started on something else.

Also check default-resource-stickiness to prevent automatic fail-back
(unless that is what you wish). 


> > property $id="cib-bootstrap-options" \
> > dc-version="1.0.9-unknown" \
> > cluster-infrastructure="openais" \
> > expected-quorum-votes="3" \
> > stonith-enabled="false" \
> > symmetric-cluster="false" \
> 
> tried symmetric-cluster="true"?
> 
> > no-quorum-policy="ignore"
> >
> >
> > tanks,
> >
> >
> 
> Regards,
> Andreas
> 
> 
> 
> 

-- 
Best Regards,

Brett Delle Grazie

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________