[ClusterLabs] Fwd: corosync works but pacemaker is started and both processes exit

[Ken Gaillot]

Hi,

Your corosync.conf uses Corosync 1 syntax. I'm not sure that's the
problem, but the first thing I would do is update it, to avoid any
complications. Try something like:

totem {
    version: 2
    cluster_name: ExampleCluster
    transport: knet
    crypto_cipher: aes256
    crypto_hash: sha256
}

quorum {
    provider: corosync_votequorum
}

logging {
    to_logfile: yes
    logfile: /var/log/cluster/corosync.log
    to_syslog: yes
    timestamp: on
}

plus your nodelist section.

On Wed, 2022-11-02 at 10:41 +0800, shiguo ma wrote:
> 
> 
> ---------- Forwarded message ---------
> 发件人： shiguo ma <mashiguo279 at gmail.com>
> Date: 2022年11月2日周三 10:35
> Subject: corosync works but pacemaker is started and both processes
> exit
> To: <developers at clusterlabs.org>
> 
> 
> tail -f /var/log/pacemaker/pacemaker.log
> Oct 28 13:46:55 node-2 pacemakerd [12941] (crm_log_init) info:
> Changed active directory to /var/lib/pacemaker/cores
> Oct 28 13:46:55 node-2 pacemakerd [12941] (ipc_post_disconnect) info:
> Disconnected from launcher IPC API
> Oct 28 13:46:55 node-2 pacemakerd [12941] (mcp_read_config) info:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY (retrying in 1s) |
> rc=2
> Oct 28 13:46:56 node-2 pacemakerd [12941] (mcp_read_config) info:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY (retrying in 2s) |
> rc=2
> Oct 28 13:46:58 node-2 pacemakerd [12941] (mcp_read_config) info:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY (retrying in 3s) |
> rc=2
> Oct 28 13:47:01 node-2 pacemakerd [12941] (mcp_read_config) info:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY (retrying in 4s) |
> rc=2
> Oct 28 13:47:05 node-2 pacemakerd [12941] (mcp_read_config) info:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY (retrying in 5s) |
> rc=2
> Oct 28 13:47:10 node-2 pacemakerd [12941] (mcp_read_config) crit:
> Could not connect to Corosync CMAP: CS_ERR_LIBRARY | rc=2
> Oct 28 13:47:10 node-2 pacemakerd [12941] (crm_exit) info: Exiting
> pacemakerd | with status 69
> vim /etc/corosync/corosync.conf
> Please read the corosync.conf.5 manual page
> totem {
> version: 2
> # Set name of the cluster
> cluster_name: ExampleCluster
> secauth: off
> # crypto_cipher and crypto_hash: Used for mutual node authentication.
> # If you choose to enable this, then do remember to create a shared
> # secret with "corosync-keygen".
> # enabling crypto_cipher, requires also enabling of crypto_hash.
> # crypto works only with knet transport
> crypto_cipher: none
> crypto_hash: none
> #transport:udpu
> }
> interface {
> ringnumber: 0 #回环号码,若主机有多块网卡,避免心跳汇流
> bindnetaddr: 60.60.60.0
> #心跳网段,corosync会自动判断本地网卡上配置的哪个IP地址是属于这个网络的，并把这个接口作为多播心跳信息传递的接口
> mcastaddr: 226.94.1.1 #心跳信息组播地址(所有节点必须一致)
> mcastport: 5405 #组播端口
> ttl: 1 #只向外多播ttl为1的报文，防止发生环路
> }
> logging {
> # Log the source file and line where messages are being
> # generated. When in doubt, leave off. Potentially useful for
> # debugging.
> fileline: off
> # Log to standard error. When in doubt, set to yes. Useful when
> # running in the foreground (when invoking "corosync -f")
> to_stderr: yes
> # Log to a log file. When set to "no", the "logfile" option
> # must not be set.
> to_logfile: yes
> logfile: /var/log/cluster/corosync.log
> # Log to the system log daemon. When in doubt, set to yes.
> to_syslog: yes
> # Log debug messages (very verbose). When in doubt, leave off.
> debug: off
> # Log messages with time stamps. When in doubt, set to hires (or on)
> #timestamp: hires
> logger_subsys {
> subsys: QUORUM
> debug: off
> }
> }
> quorum {
> # Enable and configure quorum subsystem (default: off)
> # see also corosync.conf.5 and votequorum.5
> provider: corosync_votequorum
> }
> nodelist {
> # Change/uncomment/add node sections to match cluster configuration
> node {
> 	# Hostname of the node
> 	name: node-1
> 	# Cluster membership node identifier
> 	nodeid: 1
> 	# Address of first link
> 	ring0_addr: node-1
> 	# When knet transport is used it's possible to define up to 8
> links
> 	ring1_addr: 60.60.60.84
> }
> node {
> 	# Hostname of the node
> 	name: node-2
> 	# Cluster membership node identifier
> 	nodeid: 2
> 	# Address of first link
> 	ring0_addr: node-2
> 	# When knet transport is used it's possible to define up to 8
> links
> 	ring1_addr: 60.60.60.119
> }
> # ...
> service {
> var: 0
> name: pacemaker
> }
> }
> 
> 
> 
> 
> Attached is the log in debug mode
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> ClusterLabs home: https://www.clusterlabs.org/
-- 
Ken Gaillot <kgaillot at redhat.com>