I need some help pretty badly. I was following along with this excellent write-up to create a second network for my corosyncing, and I thought it was going pretty well, but now I have all 4 of my nodes completely isolated somehow. I've attached the old and new corosync.conf files, and I've reverted all 4 to the original, but on node1 the corosync service will not start. The other 3 have it running, but don't form a quorum for some reason.
I changed the corosynf.conf file and rebooted one node. All looked well, so I rebooted a second, it paired up with the first, great, I rebooted the third, and it formed a quorum... but when I rebooted the last it would not join (node 1) it would not join the cluster. So, I tried to copy the old corosync.conf back to revert, but node1 didn't get the update, so I stopped corosync as described here and reverted it, when it all went to hell.
What to do next (without making it worse)?
Original corosync.conf (reverted to currently)
New/separated corosync.conf
Hosts File
I changed the corosynf.conf file and rebooted one node. All looked well, so I rebooted a second, it paired up with the first, great, I rebooted the third, and it formed a quorum... but when I rebooted the last it would not join (node 1) it would not join the cluster. So, I tried to copy the old corosync.conf back to revert, but node1 didn't get the update, so I stopped corosync as described here and reverted it, when it all went to hell.
What to do next (without making it worse)?
Original corosync.conf (reverted to currently)
Code:
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: svr-01
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.100.11
}
node {
name: svr-02
nodeid: 3
quorum_votes: 1
ring0_addr: 192.168.100.12
}
node {
name: svr-03
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.100.13
}
node {
name: svr-04
nodeid: 4
quorum_votes: 1
ring0_addr: 192.168.100.14
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: Congress
config_version: 6
interface {
bindnetaddr: 192.168.100.11
ringnumber: 0
}
ip_version: ipv4
secauth: on
version: 2
}New/separated corosync.conf
Code:
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: svr-01
nodeid: 1
quorum_votes: 1
ring0_addr: 1corosync
}
node {
name: svr-02
nodeid: 3
quorum_votes: 1
ring0_addr: 2corosync
}
node {
name: svr-03
nodeid: 2
quorum_votes: 1
ring0_addr: 3corosync
}
node {
name: svr-04
nodeid: 4
quorum_votes: 1
ring0_addr: 4corosync
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: Congress
config_version: 7
interface {
bindnetaddr: 192.168.102.11
ringnumber: 0
}
ip_version: ipv4
secauth: on
version: 2
}Hosts File
Code:
127.0.0.1 localhost.localdomain localhost
192.168.100.11 svr-01.bdfserver.com svr-01
192.168.100.12 svr-02.bdfserver.com svr-02
192.168.100.13 svr-03.bdfserver.com svr-03
192.168.100.14 svr-04.bdfserver.com svr-04 pvelocalhost
# corosync network hosts
192.168.102.11 1corosync.bdfserver.com 1corosync
192.168.102.12 2corosync.bdfserver.com 2corosync
192.168.102.13 3corosync.bdfserver.com 3corosync
192.168.102.14 4corosync.bdfserver.com 4corosync
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
