[Pacemaker] How to use votequorum for quorum provider?

[S, MOHAMED (MOHAMED)** CTR **]

Hi,

Yesterday someone replied on the same issue and suggested the below configuration.

> yes ... a quorum provider and there are no plugins anymore in Corosync
> 2.0 ... for two nodes you can use:
>
> quorum {
>           provider: corosync_votequorum
>           expected_votes: 2
> }
>


Reagrds,
Raffi

________________________________
From: Mars gu [mailto:gukaicorosync at 163.com]
Sent: Thursday, May 31, 2012 6:51 PM
To: pacemaker
Subject: [Pacemaker] How to use votequorum for quorum provider?

hi,
   corosync-1.4.1-3.el6.x86_64
   pacemaker-1.1.5-8.el6.x86_64

   I want to use votequorum for my quorum provider.but some problems occured.
  if my  'corosync.conf ' is like that
 *************************************
totem {
        version: 2
        secauth: off
        threads: 0
        rrp_mode: none
        interface {
                ringnumber: 0
                bindnetaddr: 192.168.10.0
    &n! bsp;           mcastaddr: 226.94.2.1
                broadcast: no
                mcastport: 4000
        }
}
logging {
        timestamp: off
        fileline: off
        function_name: off
        to_stderr: no
        to_logfile: no
        to_syslog: yes
        logfile: /var/log/cluster/corosync.log
        debug: off
        logger_subsys {
      ! ;          subsys: AMF
                debug: off
        }
}
service{
        name: corosync_quorum
        ver: 0
}
service{
        ver: 0
        name: pacemaker
        clustername: pcmk
}

quorum{
        provider: votequorum
        votes: 1
        expected_votes: 3
}
*********************************
it couldn't load the provider. the log is
***********************************
May 31 21:04:29 h10_147 corosync[2944]:  [QUORUM] Couldn't load quorum provider votequorum
May 31 21:04:29 h10_147 coro! sync[2944]:  [SERV  ] Service engine loaded: corosync cluster quorum service v0.1
***********************************

Help!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120531/dbb2c890/attachment-0003.html>