Suddenly realized it is normal because all clusters are broadcasting on the same UDP port. I changed the ports and the messages are sticking to their own clusters.
mike wrote: > I created a simple 2 node cluster, one resource with one VIP. After some > fiddling (thanks to Marian) I was able to get the cluster running smoothly. > > I repeated the same process on another 2 node cluster. VIP, working > flawlessly. > > Tonight I noticed these odd messages (lots of them) in cluster A: > Mar 25 19:25:32 DBSUAT1A.intranet.mydomain.com heartbeat: [4009]: WARN: > string2msg_ll: node [lvsuat1b.intranet.mydomain.com] failed authentication > Mar 25 19:25:32 DBSUAT1A.intranet.mydomain.com heartbeat: [4009]: WARN: > string2msg_ll: node [lvsuat1a.intranet.mydomain.com] failed authentication > Only thing is lvsuat1a and lvsuat1b are from cluster B! > > I'm seeing the reverse messages on Cluster B of course > > Both clusters are on the same subnet so I'm assuming these are messages > that the nodes in Cluster B are polling Clsuter A and cannot join > because of the different authkeys. Am I right in this assumption or is > there something funky going on? If it is normal, is there a way I can > turn off these polling messages? > > Thanks > > > > _______________________________________________ > 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
