On 2007-10-17T16:24:03, Bernd Schubert <[EMAIL PROTECTED]> wrote:
> I really think this "No local heartbeat. Forcing restart" is just ridiculous.
> Either the system is dead and then it also can't restart itself or the the
> system is in operating state, but then it also doesn't need to reset itself.
>
> So far I haven't seen this issue here with heartbeat2, but in my former group
> we had to set heartbeat1 timeouts to 4 min (!) due to the useless
> self-resetting. The system was working perfectly, local shell and other
> daemons were working without a problem, only heartbeat thought it had to shut
> itself.
> Usually this happend after a reboot of the other failover system when it did
> drbd resyncing, but as I said, this was only an issue with heartbeat.
Then the system was _not_ working well, but the scheduling latency of
the heartbeat process too high. Sorry. Kernel bug.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
