> those network recommendations are mainly for lost heartbeats respectively > cluster comm messages, not for Gmain_timeout_dispatch thingies per se.
> so maybe upgrading to a more recent kernel + pacemaker is > the _real_ solution? Thanks for the suggestions on some possible network and buffering tweaks. I might look into them if the problem continues, but I suspect you're right that the Gmain_timeout_dispatch issue is probably elsewhere. Interestingly, last night was the first time in a while that I did NOT get the "local status" delay error messages. The only thing that changed was a portion of my backup methodology. I had been doing an rsync at 11:30 PM that always took until 1:00 AM, plus a tape backup at 1:30 AM that went to 4:00 AM. Last night I didn't do the rsync. I got some "WARN: Gmain_timeout_dispatch: Dispatch function for memory stats took too long to execute" messages, but none of the usual "local status" delay messages. I'll be watching it closely. -- Eric Robinson Disclaimer - October 20, 2009 This email and any files transmitted with it are confidential and intended solely for General Linux-HA mailing list. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management and Physician's Managed Care. Warning: Although Physician Select Management and Physician's Managed Care have taken reasonable precautions to ensure no viruses are present in this email, the companies cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
