On 09.08.23 00:18, Xin Liang via Users wrote:
Hi Bartk,
Hi Jin,
What's the version of crmsh you are using?
4.5.0
Could you please provide your corosync.conf on these 2 nodes after you
meed this error?
And, if you run "crm cluster init -u -s -s -s
" on node01, crmsh will just pick up
Hi Bartk,
What's the version of crmsh you are using?
Could you please provide your corosync.conf on these 2 nodes after you meed
this error?
And, if you run "crm cluster init -u -s -s -s " on
node01, crmsh will just pick up ONE interface and write it into corosync.conf,
while I see there are
On 08.08.23 11:45, Nicholas Yang wrote:
Maybe a firewall is blocking the ports used by corosync. In a 2-node
cluster using UDPU, 4 udp streams should be seen on one of the LAN
interfaces, including:
1. from local port 5405 to remote port 5405
2. from remote port 5405 to local port 5405
3. from
> Aug 08 10:25:42 node02 corosync[20280]: [QUORUM] Members[1]: 2
> Aug 08 10:25:42 node02 corosync[20280]: [MAIN ] Completed service
synchronization, ready to provide service.
These lines suggests that corosync was not able to form a quorum with
both nodes included.
Maybe a firewall is bl
On 08.08.23 10:06, Nicholas Yang wrote:
Hi Bartk,
Hi Nicholas,
Thank you for your message and advice. I've checked the logs on node02
during the cluster joining process. I've pasted them to the Pastebin
service:
- Logs from the systemd corosync service [1]
- Logs from the systemd pacemaker
Hi Bartk,
You may look into the status and logs of service `corosync` and
`pacemaker` to check what's going wrong.
systemctl status corosync
systemctl status pacemaker
journalctl --unit corosync
journalctl --unit pacemaker
Regards,
Nicholas Yang
On 8/8/23 04:45, Bartosz Kaczyński wrote:
Hel
