[Pacemaker] new in list - corosync failover problem

[Emanuel dos Reis Rodrigues]

Follow logs attach.

The system:

Debian Lenny
Pacemaker from debian Backports


tanks,



Emanuel dos Reis Rodrigues
Senior Level Linux Professional (LPIC-3) 
LPI 302 (Mixed Environment) Specialty
C|EH Certified Ethical Hacker
http://br.linkedin.com/in/emanuelreis
emanueldosreis(No*SpAm)gmail.com
+55 95 8112-9628








Dejan Muhamedagic wrote:
> Hi,
>
> On Sun, Aug 15, 2010 at 10:30:13PM -0400, 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.
>>     
>
> Really hard to say without looking at the logs.
>
> Thanks,
>
> Dejan
>
>   
>> 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
>> property $id="cib-bootstrap-options" \
>>        dc-version="1.0.9-unknown" \
>>        cluster-infrastructure="openais" \
>>        expected-quorum-votes="3" \
>>        stonith-enabled="false" \
>>        symmetric-cluster="false" \
>>        no-quorum-policy="ignore"
>>
>>
>> tanks,
>>
>>
>> -- 
>> Emanuel dos Reis Rodrigues
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>     
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian01-corosync.log
Type: text/x-log
Size: 69926 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100816/93a1875c/attachment-0012.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian02-corosync.log
Type: text/x-log
Size: 43912 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100816/93a1875c/attachment-0013.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian03-corosync.log
Type: text/x-log
Size: 28348 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100816/93a1875c/attachment-0014.bin>