[Pacemaker] openais update

jiaju liu liujiaju86 at yahoo.com.cn
Mon Oct 18 02:00:16 UTC 2010


Hi my corosync.conf is as follows: something wrong with it?



# Please read the corosync.conf.5 manual page
compatibility: whitetank
totem {
 version: 2
 # How long before declaring a token lost (ms)
 token:          5000
 # How many token retransmits before forming a new configuration
 token_retransmits_before_loss_const: 10
 # How long to wait for join messages in the membership protocol (ms)
 join:           1000
 # How long to wait for consensus to be achieved before starting a new round of membership configuration (ms)
 consensus:      2500
 # Turn off the virtual synchrony filter
 vsftype:        none
 # Number of messages that may be sent by one processor on receipt of the token
 max_messages:   20
 # Stagger sending the node join messages by 1..send_join ms
 send_join: 45
 # Limit generated nodeids to 31-bits (positive signed integers)
 clear_node_high_bit: yes
 # Disable encryption
 secauth: off
 # How many threads to use for encryption/decryption
 threads:    0
 # Optionally assign a fixed node id (integer)
 # nodeid:         1234
 interface {
  ringnumber: 0
  # The following values need to be set based on your environment
  bindnetaddr: 10.53.11.0
  mcastaddr: 226.94.1.0
  mcastport: 5405
 }
}
logging {
        fileline: off
        to_stderr: yes
        to_logfile: yes
        to_syslog: yes
        logfile: /tmp/corosync.log
        debug: off
        timestamp: on
        logger_subsys {
                subsys: AMF
                debug: off
        }


Hi,

Just a wild guess, but in corosync.conf you have defined logfile: 
/var/log/cluster/corosync.log. Is the directory /var/log/cluster 
created? If it isn't, create it and try again.

Regards,

Dan

jiaju liu wrote:
>
>
>
>     Thank you for your help
>     I have install all rpm packages.
>     now I use order
>     service corosync start
>     the result is
>      
>     Starting Corosync Cluster Engine (corosync):               [FAILED]
>      
>     I change the corosync.conf several times it doesn't work. would
>     you please send me  a document as reference? Thanks a lot
>      
>     Hi,
>
>     It's not mandatory to install ldirectord, I know it's not a
>     dependency
>     anymore. As for libesmtp see http://tinyurl.com/2uhdpzw
>
>     jiaju liu wrote:
>     > Hi I have already installed rpm as follow:
>     > cluster-glue-1.0.5-1.el5.x86_64.rpm
>     > cluster-glue-libs-1.0.5-1.el5.x86_64.rpm
>     > cluster-glue-libs-devel-1.0.5-1.el5.x86_64.rpm
>     > corosync-1.2.2-1.1.el5.x86_64.rpm
>     > corosynclib-1.2.2-1.1.el5.x86_64.rpm
>     > corosynclib-devel-1.2.2-1.1.el5.x86_64.rpm
>     > heartbeat-3.0.3-2.el5.x86_64.rpm
>     > heartbeat-devel-3.0.3-2.el5.x86_64.rpm
>     > heartbeat-libs-3.0.3-2.el5.x86_64.rpm
>     > openais-1.1.0-1.el5.x86_64.rpm
>     > openaislib-1.1.0-1.el5.x86_64.rpm
>     > openaislib-devel-1.1.0-1.el5.x86_64.rpm
>     > pacemaker-libs-devel-1.0.8-6.1.el5.x86_64.rpm
>     > pacemaker-libs-1.0.8-6.1.el5.x86_64.rpm
>     > resource-agents-1.0.3-2.el5.x86_64.rpm
>     > 
>     > 
>     > at last I install pacemaker-1.0.8-6.1.el5.x86_64.rpm
>     > it shows
>     > error: Failed dependencies:
>     >  libesmtp is needed by pacemaker-1.0.8-6.1.el5.x86_64
>     >  libesmtp.so.5()(64bit) is needed by pacemaker-1.0.8-6.1.el5.x86_64
>     > 
>     > and the ldirectord-1.0.3-2.el5.x86_64.rpm is must be installed?
>     > thanks a lot:-)
>     >
>     >
>     >   
>
>     -- 
>     Dan FRINCU
>     Systems Engineer
>     CCNA, RHCE
>     Streamwide Romania
>
>     -------------- next part --------------
>     An HTML attachment was scrubbed...
>     URL:
>     <http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20101015/a1ea4614/attachment-0001.htm>
>
>
>  



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101018/8a680e6c/attachment-0001.html>


More information about the Pacemaker mailing list