Hi Michael, I have managed to successfully configure corosync with udpu, it unfortunately hasn't made a difference in the behaviour of the cluster.
I have found that I don't even need to restart the host in order to get this behaviour - all I need to do is stop and restart corosync and pacemaker on *one* of the hosts. To be precise: I've been able to narrow it down to only one of the two hosts (r3). If I reboot the host, or restart the services on r4 everything works fine. If I try the same with r3, I have problems. I feel as though the answer may lie in the logfiles, the intercommunication between the individual components of the HA software makes it a bit difficult to accurately read the logfiles as an outsider to this software. I have attached the logs of both r3 and r4 after reproducing this effect this afternoon, they are much shorter to read than those previously: corosync-r3.log: http://pastebin.com/ZAhh5nax corosync-r4.log: http://pastebin.com/SETtqnZM Are there any other steps I could take in debugging this behaviour? Regards, James On 10/26/2012 04:33 PM, Michael Schwartzkopff wrote: >> Hi Michael, >> >> I'm working with a Linux From Scratch based kernel (version 3.4.7) >> running in a virtual machine and with virtual switches. > (...) >> `tcpdump -ni eth1 port 5404` returns: >> >> listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes >> 16:22:27.849551 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> 16:22:28.210578 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> 16:22:28.770181 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> 16:22:28.989802 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> 16:22:29.370684 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> 16:22:29.751062 IP 192.168.200.166.5404 > 224.0.0.18.5405: UDP, length 87 >> >> Every now and then there is a packet from r4 (192.168.200.170), it does >> appear as though r4 is quite quiet though. > > Ah. No pakcets from 192.168.200.166 unicast? Please try to configure unicast > in > your corosync configuration. See the udpu README file of corosync. > > I had the same problem and the cause was the the virtual bridge or KVM dropped > all multicast packets. > > Greetings, > > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
