Re: [Linux-HA] Heartbeat errors related to Gmain_timeout_dispatch at low traffic

2013-11-20 Thread Savita Kulkarni
Hi Lars,

We observed one pattern with these errors - at most of the case,on both VMs
, these errors came at the same time.
We are suspecting either network issue in that case only late heartbeat
error will come not Gmain_timeout_dispatch related errors right ? or
VM is getting paused for sometime for some reason and when it is resumed
Gmain_timeout_dispatch/late heartbeat errors are coming.
We are investigating more on this.


@heartbeat 3 - for this issue most of the time advice given was to upgrade.
But we are using same heartbeat version
in other setups also and it is working fine there.

What do you think?

Regards,
Savita


On Tue, Nov 19, 2013 at 4:23 PM, Lars Ellenberg
lars.ellenb...@linbit.comwrote:

 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 (
  1 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

___
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


[Linux-HA] Heartbeat errors related to Gmain_timeout_dispatch at low traffic

2013-11-14 Thread Savita Kulkarni
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 (
1 ms) before being called (GSource: 0x13892f58)

Can anyone tell me what can be the issue?

Can it be a hardware issue?


Regards,

Savita
___
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