Attached, please find an hb_report created for this particular setup for the timeframe when the issue occurred.
I realize that we're not supposed to sanitize these because it could obfuscate important information, but I've had to go through and sed replace a bunch of stuff for security reasons. I hope I didn't destroy anything useful to troubleshooting. Also, I noticed that I almost _always_ get one of these G_SIG_dispatch delays in the logs at the time when the daily report information is output. On Tue, 2008-06-17 at 14:29 -0400, Greg Haase wrote: > Last week I emailed the list regarding a node failover that occurred > when IPAddr monitor timed out. At the same time, my log was showing > G_SIG_dispatch delays in lrmd. The thread ended in a petty discussion > over what was the proper time out value (although all the examples on > linux-ha.org show 3s here, it was suggested that I bump mine from 5s to > 15s). > > A few minutes ago, I experienced another failover, this one due to drbd > monitor failure. None of my other logs show any kind of disk error. In > fact, my MySQL error log (located on the very drbd disk that failed) > shows the shutdown messages subsequently issued by heartbeat. Again, the > monitor failure occurs at the same time that a G_SIG_display delay > occurs. > > Now does anyone have any idea why these errors may be occurring and is > there a way to resolve them. > > Please see attached log snippet. > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
hb_report.tar.gz
Description: application/compressed-tar
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
