corosync的两个节点处于脱机状态

我看到: 这个问题 。

192.168.2.0/24 – 与GW的办公室networking .2.1

根据Corosync文档,如果本地接口为192.168.5.67,networking掩码为255.255.255.0,则将bindnetaddr设置为192.168.5.0。

corosync.conf

totem { version: 2 crypto_cipher: none crypto_hash: none interface { ringnumber: 0 bindnetaddr: 192.168.2.0 mcastaddr: 239.255.1.1 mcastport: 5405 ttl: 1 } } logging { fileline: off to_stderr: no to_logfile: yes logfile: /var/log/cluster/corosync.log to_syslog: yes debug: off timestamp: on logger_subsys { subsys: QUORUM debug: off } } quorum { provider: corosync_votequorum } service { name: pacemaker ver: 1 } nodelist { node { ring0_addr: KVM-1 nodeid: 1 } node { ring0_addr: KVM-2 nodeid: 2 } node { ring0_addr: KVM-3 nodeid: 3 } } 

crm状态

 Stack: corosync Current DC: KVM-1 (version 1.1.13-10.el7_2.2-44eb2dd) - partition WITHOUT quorum 3 nodes and 0 resources configured Online: [ KVM-1 ] OFFLINE: [ KVM-2 KVM-3 ] 

tcpdump日志

 [oneadmin@KVM-1 corosync]$ sudo tcpdump -i ovs-br0 -n port 5405 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ovs-br0, link-type EN10MB (Ethernet), capture size 65535 bytes 20:17:15.561824 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:15.864866 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:16.167969 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:16.471014 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:16.774051 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:17.077136 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:17.380149 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 20:17:17.683214 IP 192.168.2.67.hpoms-dps-lstn > 239.255.1.1.netsupport: UDP, length 87 

所有节点必须处于在线状态? 我哪里有错误?

您正在尝试组播通信,这需要在底层networking上提供支持。 对于三个节点,我认为最安全的select是切换到unicast (也就是通常发送到每个主机自己的IP地址192.168.2.x)。