Hey all,
Finally got some time to check this on our servers and build up a separate test
cluster and I found the issue, no debugging required. Seems we are/were using
IP addresses instead of names in the corosync.conf. I replicated that with the
separate test cluster and noticed the exact same
On 24/04/2023 22:16, Tyler Phillippe via Users wrote:
Hello all,
We are currently using RHEL9 and have set up a PCS cluster. When restarting the
servers, we noticed Corosync 3.1.5 doesn't start properly with the below error
message:
Parse error in config: No valid name found for local host
Hi,
With Corosync 3, node names must be specified in
/etc/corosync/corosync.conf like:
node {
ring0_addr: node1
name: node1
nodeid: 1
}
(ring0_addr is a resolvable name used to identify the interface, and
name is the name that should be used in the cluster)
If
Hello all,
We are currently using RHEL9 and have set up a PCS cluster. When restarting the
servers, we noticed Corosync 3.1.5 doesn't start properly with the below error
message:
Parse error in config: No valid name found for local host
Corosync Cluster Engine exiting with status 8 at
