On Thu, Jun 11, 2020 at 09:46:14AM +0200, Jan Friesse wrote: > > Jan, > > > > actually we using this. > > > > [root@lvm-nfscpdata-05ct::~ 100 ]# apt show corosync > > Package: corosync > > Version: 3.0.1-2+deb10u1 > > > > [root@lvm-nfscpdata-05ct::~]# apt show libknet1 > > Package: libknet1 > > Version: 1.8-2 > > > > This are the newest version provided on Mirror. > > yup, but these are pretty old anyway and there is quite a few bugs (and many > of them may explain behavior you see). > > I would suggest you to either try a upstream code compilation or (if you > need to stick with packages) you may give a try sid packages or Proxmox > repositories (where knet is at version 1.15 and corosync 3.0.3).
I can't seem to reproduce this with Debian versions mentioned above on 3 nodes with 3 links. Can you check for each of the interfaces if the traffic flows in both directions and also there is no DROP rule in firewall after arrival? For example on node2: root@node2:~# tcpdump -pni ens7 src 192.168.44.11 root@node2:~# tcpdump -pni ens7 dst 192.168.44.11 root@node2:~# tcpdump -pni ens7 src 192.168.44.13 root@node2:~# tcpdump -pni ens7 dst 192.168.44.13 root@node2:~# tcpdump -pni ens8 src 10.0.44.11 root@node2:~# tcpdump -pni ens8 dst 10.0.44.11 root@node2:~# tcpdump -pni ens8 src 10.0.44.13 root@node2:~# tcpdump -pni ens8 dst 10.0.44.13 Also logs from corosync when this happens would be useful. -- Valentin _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/