[Linux-HA] messages from existing hearbeat on the same lan

2010-01-19 Thread Aclhk Aclhk
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.




  Yahoo!香港提供網上安全攻略,教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: [Linux-HA] messages from existing hearbeat on the same lan

2010-01-19 Thread Dominik Klein
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?
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


Re: [Linux-HA] messages from existing hearbeat on the same lan

2010-01-19 Thread Andrew Beekhof
On Tue, Jan 19, 2010 at 1:15 PM, Dominik Klein d...@in-telegence.net 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
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems