Re: [ClusterLabs] Minor bug in SLES 15 corosync-2.4.5-6.3.2.x86_64 (unicast, ttl)

Ulrich, Hi! A short notification: I had set up a new cluster using udpu, finding that ringnumber 0 has a ttl statement ("ttl:1"), but ringnumber 1 had not. So I added one for ringnumber 1, and then I reloaded corosync via corosync-cfgtool -R. probably ttl with value different from 1

Re: [ClusterLabs] egards, Q: what does " corosync-cfgtool -s" check actually?

Ulrich, Hi! having a problem, I wonder what " corosync-cfgtool -s" does check actually: I see on all nodes and all rings "status = ring 0 active with no faults", but the nodes seem unable to comminicate somehow. For UDPU/UDP without RRP it will always display "ring 0 active with no

Re: [ClusterLabs] egards, Q: what does " corosync-cfgtool -s" check actually?

On 11/20/20 8:22 AM, Ulrich Windl wrote: > Hi! > > having a problem, I wonder what " corosync-cfgtool -s" does check actually: > I see on all nodes and all rings "status = ring 0 active with no faults", > but the nodes seem unable to comminicate somehow. > I there a kind of "corosync node ping"