On Fri, Aug 24, 2007 at 09:35:13AM -0600, [EMAIL PROTECTED] wrote: > > I'll try to get a core dump, in the meantime has anyone else seen this > issue?
Internet search results: http://lists.community.tummy.com/pipermail/linux-ha/2005-April/014427.html http://lists.community.tummy.com/pipermail/linux-ha/2005-September/016052.html These two are by Alan who knows by far the most about this stuff. He suggests going to the newer generation Heartbeat. You can still run your v1 config on that. Is that available for your release? Otherwise, it seems like getting a core dump won't be easy either: seems like a code change would probably be required. > On Thu, 23 Aug 2007 23:50:09 +0200, "Dejan Muhamedagic" > <[EMAIL PROTECTED]> said: > > On Thu, Aug 23, 2007 at 03:28:03PM -0600, [EMAIL PROTECTED] wrote: > > > > > > This is a follow up question concerning upgrading the kernel on a Redhat > > > EL 3 two node cluster. > > > The systems currently run 2.4.21-32.0.1.ELsmp and we need to upgrade to > > > 2.4.21-51.ELsmp. The heartbeat rpms are the following: > > > > > > heartbeat-ldirectord-1.2.3-2.rh.el.3.0 > > > heartbeat-1.2.3-2.rh.el.3.0 > > > heartbeat-pils-1.2.3-2.rh.el.3.0 > > > heartbeat-stonith-1.2.3-2.rh.el.3.0 > > > > Well, this is all very old. A conservative shop you have there, > > right? > > > > > After upgrading the kernel on one on the systems, rebooting and starting > > > heartbeat things seem to function for about a minute, then the heartbeat > > > shuts itself down and tries to restart itself continuesly. In the > > > ha-log the following occurs: > > > > > > heartbeat: 2007/08/23_13:53:39 ERROR: Exiting HBWRITE process 1998 > > > killed by signal 11. > > > heartbeat: 2007/08/23_13:53:39 ERROR: Core heartbeat process died! > > > Restarting. > > > heartbeat: 2007/08/23_13:53:39 WARN: Shutdown delayed until current > > > resource activity finishes. > > > > The write process (medium-wise) segfaults. Could you pass the > > backtrace of a core dump. > > > > > The rest of the entries are "info" type. A reboot and selection of the > > > original kernel and everything functions as it should and the above > > > errors do not occur. Anyway to fix this or is there a work around. We > > > need to run this cluster until we can schedule a rebuild, but are > > > required to update the kernel. > > > > > > Thanks for any help. > > > _______________________________________________ > > > 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 > _______________________________________________ > 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
