On Tue, Jan 19, 2010 at 1:15 PM, Dominik Klein <[email protected]> wrote: > Aclhk Aclhk wrote: >> On the same lan, there are already two heartbeat node 136pri and 137sec. >> >> I setup another 2 nodes with heartbeat. they keep receiving the following >> messages: >> >> heartbeat[9931]: 2010/01/19_10:53:01 WARN: string2msg_ll: node [136pri] >> failed authentication >> heartbeat[9931]: 2010/01/19_10:53:02 WARN: Invalid authentication type [1] >> in message! >> heartbeat[9931]: 2010/01/19_10:53:02 WARN: string2msg_ll: node [137sec] >> failed authentication >> heartbeat[9931]: 2010/01/19_10:53:02 WARN: Invalid authentication type [1] >> in message! >> >> ha.cf >> debugfile /var/log/ha-debug >> logfile /var/log/ha-log >> logfacility local0 >> bcast eth0 >> keepalive 5 >> warntime 10 >> deadtime 120 >> initdead 120 >> auto_failback off >> node 140openfiler1 >> node 141openfiler2 >> >> bcast for all nodes are same, that is eth0 >> >> pls advise how to avoid the messages. > > Use mcast or ucast instead of bcast?
Or change the port _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
