[Linux-HA] Re: deadtime, warntime, and drbd

Jason Joines support at bus.okstate.edu
Wed Mar 9 07:32:56 MST 2005


Lars Marowsky-Bree wrote:

>On 2005-03-08T12:27:55, Jason Joines <support at bus.okstate.edu> wrote:
>
>  
>
>>>1. You only have ONE heartbeat channel according to these logs. That's
>>>BROKEN.
>>>
>>>      
>>>
>>   I think I have two channels if this is what you meant.  Each node is 
>>supposed to communicate with the other over both eth0 and eth1 and with 
>>the router over eth0.
>>    
>>
>
>OK, that's in your configuration, but if you look at the logs, eth0
>_never_ is reported as up or down. Indeed I missed that it's reported as
>being used, but it never seems to be working even for a single packet.
>
>I'd suggest investigating that - maybe some firewall rule?
>
>
>Hmmm, strange, such a message should have occured about 7 minutes
>earlier. Maybe the switch rebooted, or the network interface truely got
>stuck.
>
>This will be less of a problem if you figure out what keeps eth0 from
>working for you ;-)
>
>Good luck!
>
>
>Sincerely,
>    Lars Marowsky-Brée <lmb at suse.de>
>  
>

    Found it, an unbelievably stupid error on my part.  I can't believe 
I missed it and I checked several times.

# eth0 heartbeat firewall rule from nodea
iptables -A INPUT -p udp -s 172.18.88.93 --dport 694

# eth0 heartbeat firewall rule from nodeb
iptables -A INPUT -p udp -s 172.18.89.67 --dport 694

    Notice the missing "-j ACCEPT".  Now I have the missing messages in 
the logs:

Mar  9 08:22:02 nodea heartbeat[16280]: info: Link nodeb:eth0 up.
Mar  9 08:22:04 nodeb heartbeat[7691]: info: Link nodea:eth0 up.


Thanks again,

Jason
===========




More information about the Linux-HA mailing list