Copyright Notice: Welcome to reprint, but please indicate the source and author of the article. https://blog.csdn.net/handsomehuo/article/details/90607455
I recently configured pacemaker + corosync when trying to modify the address bindnetaddr of corosync.conf file (want to change 10.0.0.0), but after the execution, the command View:
corosync-cfgtool -sFound that the configuration is not in effect, heartbeat still choose the original IP address (192.168.122.0) heartbeat is detected.
By logging view, there is no obvious errors:
[root@node1 ~] tailf -n 100 /var/log/cluster/corosync.log
...
[2289] node2 corosyncnotice [TOTEM ] A new membership (192.168.122.60:316) was formed. Members joined: 1
[2289] node2 corosyncnotice [QUORUM] Members[3]: 1 3 2
[2289] node2 corosyncnotice [MAIN ] Completed service synchronization, ready to provide service.
[2289] node2 corosyncnotice [MAIN ] Node was shut down by a signal
[2289] node2 corosyncnotice [SERV ] Unloading all Corosync service engines.
[2289] node2 corosyncinfo [QB ] withdrawing server sockets
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync vote quorum service v1.0
[2289] node2 corosyncinfo [QB ] withdrawing server sockets
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync configuration map access
[2289] node2 corosyncinfo [QB ] withdrawing server sockets
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync configuration service
[2289] node2 corosyncinfo [QB ] withdrawing server sockets
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync cluster closed process group service v1.01
[2289] node2 corosyncinfo [QB ] withdrawing server sockets
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync cluster quorum service v0.1
[2289] node2 corosyncnotice [SERV ] Service engine unloaded: corosync profile loading service
[2289] node2 corosyncnotice [MAIN ] Corosync Cluster Engine exiting normally
[18475] node2 corosyncnotice [MAIN ] Corosync Cluster Engine ('2.4.3'): started and ready to provide service.
[18475] node2 corosyncinfo [MAIN ] Corosync built-in features: dbus systemd xmlconf qdevices qnetd snmp libcgroup pie relro bindnow
[18475] node2 corosyncwarning [MAIN ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
[18475] node2 corosyncwarning [MAIN ] Please migrate config file to nodelist.
[18475] node2 corosyncnotice [TOTEM ] Initializing transport (UDP/IP Unicast).
[18475] node2 corosyncnotice [TOTEM ] Initializing transmit/receive security (NSS) crypto: none hash: none
[18475] node2 corosyncnotice [TOTEM ] The network interface [192.168.122.117] is now up.
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync configuration map access [0]
[18475] node2 corosyncinfo [QB ] server name: cmap
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync configuration service [1]
[18475] node2 corosyncinfo [QB ] server name: cfg
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
[18475] node2 corosyncinfo [QB ] server name: cpg
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync profile loading service [4]
[18475] node2 corosyncnotice [QUORUM] Using quorum provider corosync_votequorum
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
[18475] node2 corosyncinfo [QB ] server name: votequorum
[18475] node2 corosyncnotice [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
[18475] node2 corosyncinfo [QB ] server name: quorum
[18475] node2 corosyncnotice [TOTEM ] adding new UDPU member {192.168.122.60}
[18475] node2 corosyncnotice [TOTEM ] adding new UDPU member {192.168.122.117}
[18475] node2 corosyncnotice [TOTEM ] adding new UDPU member {192.168.122.114}
[18475] node2 corosyncnotice [TOTEM ] A new membership (192.168.122.117:320) was formed. Members joined: 2
[18475] node2 corosyncnotice [TOTEM ] A new membership (192.168.122.60:324) was formed. Members joined: 1
[18475] node2 corosyncnotice [QUORUM] This node is within the primary component and will provide service.
[18475] node2 corosyncnotice [QUORUM] Members[2]: 1 2
[18475] node2 corosyncnotice [MAIN ] Completed service synchronization, ready to provide service.
[18475] node2 corosyncnotice [TOTEM ] A new membership (192.168.122.60:328) was formed. Members joined: 3
[18475] node2 corosyncwarning [CPG ] downlist left_list: 0 received in state 0
[18475] node2 corosyncnotice [QUORUM] Members[3]: 1 3 2
[18475] node2 corosyncnotice [MAIN ] Completed service synchronization, ready to provide service.
...By comparing the configuration file, there is no spelling errors:
[root@node1 ~]# egrep -v '(#|^$)' /etc/corosync/corosync.conf.example
totem {
version: 2
crypto_cipher: none
crypto_hash: none
interface {
ringnumber: 0
bindnetaddr: 192.168.1.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 {
}
After checking the network, hosts file (add all the relevant node ip), no problem, when unable to do anything, try to modify the IP address, nodelist section:
[root@node2 corosync]# vim corosync.conf
...
node {
ring0_addr: 10.0.0.10
nodeid: 1
}
node {
ring0_addr: 10.0.0.20
nodeid: 2
}
node {
ring0_addr: 10.0.0.30
nodeid: 3
}
}
...Run pcs cluster sync error:
[root@node1 corosync]# pcs cluster sync
10.0.0.10: {"notauthorized":"true"}
Unable to authenticate to 10.0.0.10 - (HTTP error: 401), try running 'pcs cluster auth'
Error: Unable to set corosync config: Unable to authenticate to 10.0.0.10 - (HTTP error: 401), try running 'pcs cluster auth'The reason is found, the original new IP address is not doing pcs auth, execute command and see, the problem is solved
[root@node1 corosync]# pcs cluster auth 10.0.0.10 10.0.0.20 10.0.0.30
Username: hacluster
Password:
10.0.0.30: Authorized
10.0.0.20: Authorized
10.0.0.10: Authorized
[root@node1 corosync]# pcs cluster sync
10.0.0.10: Succeeded
10.0.0.20: Succeeded
10.0.0.30: Succeeded
[root@node1 corosync]# pcs cluster start --all
10.0.0.10: Starting Cluster (corosync)...
10.0.0.20: Starting Cluster (corosync)...
10.0.0.30: Starting Cluster (corosync)...
10.0.0.30: Starting Cluster (pacemaker)...
10.0.0.10: Starting Cluster (pacemaker)...
10.0.0.20: Starting Cluster (pacemaker)...
[root@node1 corosync]# corosync-cfgtool -s
Printing ring status.
Local node ID 1
RING ID 0
id = 10.0.0.10
status = ring 0 active with no faults
To sum up:
1, if it is a new category of heartbeat IP address, you need to add in the conf configuration file:
rrp_mode:activeAt this point you do not need to add or modify parts nodelist pcs auth, the original IP address of the node will be able to update and found that when two IP network adapter are dawdle out, fence mechanism starts, node restart.
2, if it is to replace the IP address heartbeat, the need for a new address re pcs auth, which will lead to the number of nodes double pacemaker found (such as the original discovery of three nodes, which erupted added a 3, but in fact is a machine the two different IP only), where the author without making in-depth study, so the proposal is still in the planning of IP consider good planning.