[Pacemaker] [Problem]It does not start by single node configuration.

renayama19661014 at ybb.ne.jp renayama19661014 at ybb.ne.jp
Fri Jan 29 03:53:27 UTC 2010


Hi Andrew,

> Very odd. CTS (successfully) tests this condition all the time.
> 
> What does corosync.conf look like?  Is there a firewall involved?
> It _looks_ like the crmd isn't getting its own messages back.
> 

My test environment is next.

 * Single VM(RHEL5.4-32bit) on Esxi.
 * NIC x 3
  * 1: A service network.(Esxi Private Only - VM only) 
  * 2: A interconnect network(1).(Esxi Private Only - VM only)
  * 3: A interconnect network(2).(Esxi Private Only - VM only)

----------corosync.conf--------------------------
# Please read the corosync.conf.5 manual page
compatibility: whitetank
aisexec {
        user: root
        group: root
}
service {
        name: pacemaker
        ver: 0
#       use_mgmtd: yes
#       use_logd:yes
}
totem {
    version: 2
    secauth: off
    threads: 0
    rrp_mode: active
    token: 24000
    clear_node_high_bit: yes
    rrp_problem_count_timeout: 30000
        interface {
                ringnumber: 0
                bindnetaddr: 192.168.50.1
                mcastaddr: 226.94.1.1
                mcastport: 5405
        }
        interface {
                ringnumber: 1
                bindnetaddr: 192.168.60.1
                mcastaddr: 226.94.1.1
                mcastport: 5405
        }
}

logging {
        fileline: on
        to_syslog: yes
        syslog_facility: local1
        syslog_priority: debug
        debug: on
        timestamp: on
}

amf {
        mode: disabled
}


> Could you possibly retest with debug on?
Please wait....

Best Regards,
Hideo Yamauchi.





More information about the Pacemaker mailing list