[Xen-bugs] [Bug 355] New: heartbeat (1.2.6 and 2.0.2) does not run on top of dom0

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=355

           Summary: heartbeat (1.2.6 and 2.0.2) does not run on top of dom0
           Product: Xen
           Version: 2.0
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: paysen@xxxxxxxxxxxxxxxxxx


installed vanilla xen 2.0.7 with adapted xen0 .config for my nics. installed
debian sarge in dom0. compiled and installed heartbeat 1.2.6 and 2.0.2.
heartbeats are sent over eth1 via crosscable. when i start heartbeat on both
ha-nodes after a while (~40 seconds) heartbeat thinks one or both nodes are 
dead.

from ha-log:
heartbeat[2411]: 2005/10/20_14:37:24 WARN: node lilo: is dead
heartbeat[2411]: 2005/10/20_14:37:24 WARN: node labor-7: is dead
heartbeat[2411]: 2005/10/20_14:37:24 ERROR: No local heartbeat. Forcing restart.

from the heartbeat FAQ:

I got this message "ERROR: No local heartbeat. Forcing shutdown" and
then Heartbeat shut itself down for no reason at all!
        First of all, Heartbeat never shuts itself down for no reason at
        all. This kind of occurrence indicates that Heartbeat is not
        working properly, which in our experience can be caused by one
        of two things: 
              * System under heavy I/O load, or 
                
              * Kernel bug. 
                
        For how to deal with the first occurrence (heavy load), please
        read the answer to the next FAQ item. If your system was not
        under moderate to heavy load when it got this message, you
        probably have the kernel bug. The 2.4.18-2.4.20 Linux kernels
        had a bug in it which would cause it to not schedule Heartbeat
        for very long periods of time when the system was idle, or
        nearly so. If this is the case, you need to get a kernel that
        isn't broken.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs