I don't think this is legal: service {****
name: corosync_quorum**** ver: 0**** name: pacemaker**** use_mgmtd: yes**** use_logd: yes**** } and even if it were, corosync's native quorum implementation (or our use of it) was a but buggy last time i checked. On Sat, May 28, 2011 at 2:19 AM, Roman Schartlmüller < roman_schartlmuel...@gmx.at> wrote: > Hi, **** > > ** ** > > I have Problems with corosync-quorumtool. I have set up a cluster with 2 > nodes which uses corosync. **** > > For testing purposes, I am trying to establish a quorum to the cluster, > because I want to understand the quorum-corosync tool. **** > > I want to tag a node with 2 votes so that it can continue on failure and > doesn't stop to run all resources. **** > > Unfortunately, the node with 2 out of 3 votes loses yet always the quorum. > **** > > ** ** > > Can anybody please help me with configuration? Maybe there is something > wrong.**** > > ** ** > > Thanks!**** > > Best regards,**** > > Roman**** > > ** ** > > Node1:**** > > # less /etc/corosync/corosync.conf**** > > ...**** > > service {**** > > name: corosync_quorum**** > > ver: 0**** > > name: pacemaker**** > > use_mgmtd: yes**** > > use_logd: yes**** > > }...**** > > quorum {**** > > provider: corosync_votequorum**** > > expected_votes: 3**** > > votes: 2**** > > }**** > > ** ** > > #corosync-quorumtool -s**** > > Version: 1.3.1**** > > Nodes: 2**** > > Ring ID: 19936**** > > Quorum type: corosync_votequorum**** > > Quorate: Yes**** > > Node votes: 2**** > > Expected votes: 3**** > > Highest expected: 3**** > > Total votes: 3**** > > Quorum: 2 **** > > Flags: Quorate**** > > ** ** > > #corosync-quorumtool -l**** > > Nodeid Votes Name**** > > 553756864 2 192.168.200.33**** > > 570534080 2 192.168.200.34**** > > ** ** > > Node2:**** > > # less /etc/corosync/corosync.conf**** > > ...**** > > service {**** > > name: corosync_quorum**** > > ver: 0**** > > name: pacemaker**** > > use_mgmtd: yes**** > > use_logd: yes**** > > }...**** > > quorum {**** > > provider: corosync_votequorum**** > > expected_votes: 3**** > > votes: 1**** > > }**** > > ** ** > > #corosync-quorumtool -s**** > > Version: 1.3.1**** > > Nodes: 2**** > > Ring ID: 19936**** > > Quorum type: corosync_votequorum**** > > Quorate: Yes**** > > Node votes: 1**** > > Expected votes: 3**** > > Highest expected: 3**** > > Total votes: 3**** > > Quorum: 2 **** > > Flags: Quorate**** > > ** ** > > #corosync-quorumtool -l**** > > Nodeid Votes Name**** > > 553756864 1 192.168.200.33**** > > 570534080 1 192.168.200.34**** > > ** ** > > #crm configure show**** > > expected-quorum-votes="2" \**** > > dc-version="1.1.5-1.fc14-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \**** > > cluster-infrastructure="openais" \**** > > last-lrm-refresh="1306499083" \**** > > stonith-enabled="false" \**** > > no-quorum-policy="ignore"**** > > ** ** > > ** ** > > ** ** > > _______________________________________________ > Pacemaker mailing list: Pacemaker@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@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