On Thu, Nov 14, 2013 at 04:46:16PM +0530, Savita Kulkarni wrote: > Hi, > > Recently we are seeing lots of heartbeat errors related to > Gmain_timeout_dispatch > on our system. > I checked on mailing list archives if other people have faced this issue. > There are few email threads regarding this but people are seeing this issue > in case of high load. > > On our system there is very low/no load is present. > > We are running heartbeat on guest VMs, using VMWARE ESXi 5.0. > We have heartbeat -2.1.3-4 > It is working fine without any issues on other other setups and issue is > coming only on this setup. > > Following types of errors are present in /var/log/messages > > Nov 12 09:58:43 heartbeat: [23036]: WARN: Gmain_timeout_dispatch: > Dispatch function for send local status was delayed 15270 ms (> 1010 > ms) before being called (GSource: 0x138926b8) > Nov 12 09:59:00 heartbeat: [23036]: info: Gmain_timeout_dispatch: > started at 583294569 should have started at 583293042 > Nov 12 09:59:00 heartbeat: [23036]: WARN: Gmain_timeout_dispatch: > Dispatch function for update msgfree count was delayed 33960 ms (> > 10000 ms) before being called (GSource: 0x13892f58) > > Can anyone tell me what can be the issue? > > Can it be a hardware issue?
Could be many things, even that, yes. Could be that upgrading to recent heartbeat 3 helps. Could be that there is to little load, and your virtualization just stops scheduling the VM itself, because it thinks it is underutilized... Does it recover if you kill/restart heartbeat? -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
