Hi, On Mon, Jul 20, 2009 at 12:18:29PM +1000, Oliver Hookins wrote: > I've got a reasonably new installation of Heartbeat 2.99 and Pacemaker 1.0.4 > and noticed today that a heartbeat process was taking all of the CPU time on > one core. The other node in the cluster had failed and the following lines > were spewing into the ha-log continually: > > heartbeat[3663]: 2009/07/20_11:56:54 WARN: Gmain_timeout_dispatch: Dispatch > function for retransmit request > took too long to execute: 190 ms (> 10 ms) (GSource: 0x21ae6e50) > heartbeat[3663]: 2009/07/20_11:56:55 WARN: Gmain_timeout_dispatch: Dispatch > function for retransmit request > took too long to execute: 200 ms (> 10 ms) (GSource: 0x21a52810) > heartbeat[3663]: 2009/07/20_11:56:55 WARN: Gmain_timeout_dispatch: Dispatch > function for retransmit request > took too long to execute: 190 ms (> 10 ms) (GSource: 0x21a528d0) > heartbeat[3663]: 2009/07/20_11:56:55 WARN: Gmain_timeout_dispatch: Dispatch > function for retransmit request > took too long to execute: 190 ms (> 10 ms) (GSource: 0x21a52990) > > The log is now over 100MB. Any ideas what might be going on?
Can't recall seeing that. Does it persist? If so, can you send the offending process the ABRT signal and then create a report with hb_report? BTW, the log messages are just an artifact of the high load. Thanks, Dejan > -- > Regards, > Oliver Hookins > Anchor Systems > _______________________________________________ > 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
