[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-ha-dev
Subject: Re: [Linux-ha-dev] Problem WARN: Gmain_timeout_dispatch Again
From: gilmarlinux () agrovale ! com ! br
Date: 2011-05-16 21:22:41
Message-ID: 48046.201.24.133.203.1305580961.squirrel () mail ! agrovale ! com ! br
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Ok,Thank you. I'm trying to isolate the problem to the maximum, so I try to diagnose \
the problem. I've tried tools like sar iostat to check the system queries. But for \
now everything without problems
> That's probably OK. If you're really having a problem, it should>
ordinarily show it up before it causes a false failover.> > Then you
can figure out if you want to raise your timeout or figure out> what's causing
the slow processing.> > > On 05/14/2011 09:08 AM,
gilmarlinux@agrovale.com.br wrote:>> Thanks again.>> deadtime 30
and warntime 15 this good ?>>>> > BUT also either make
warntime smaller or deadtime larger...>> >>> >>> > On 5/13/2011 7:48 PM, \
gilmarlinux@agrovale.com.br wrote:>>
> > Thank you for your attention.>> >> His recommendation and
wait, if only to continue the logs I get>> >> following warning if the
services do not migrate to another server>> >> just keep watching the
logs warning.>> >>>> >> > I typically make
deadtime something like 3 times warntime. That way>> >> > you'll
get data before you get into trouble. When your heartbeats>> >> >
exceed warntime, you get information on how late it is. I would>> >>
> typically make deadtime AT LEAST twice the latest time you've>> ever
seen>> >> > with warntime.>> >> >>> >> > If the worst case you ever saw was this 60ms \
instead of 50ms, I'd>> look>> >> > somewhere else for the problem.
However, it is possible that you>> have a>> >> >
hardware trouble, or a kernel bug. Possible, but unlikely.>> >>
> > > > > > More logs are always good when looking at a problem
like this.>> >> > hb_report will get you lots of logs and so on for
the next time it>> >> happens.>> >> >>> >> > On 05/13/2011 11:44 AM, \
gilmarlinux@agrovale.com.br wrote:>> >> >> Thanks for the help.>> >> >>>> >> >> I had \
a problem the 30 days that began with this post, and after two>> >> >> days the \
heartbeat message that the accused had fallen server1 and>> >> >> services migrated \
to server2>> >> >> Now with this change to eth1 and eth2 for drbd and heartbeat to \
the>> >> >> amendment of warntime deadtime 20 to 15 and do not know if this will>> >> \
>> happen again.>>
> > > > Thanks>> >> >>>> >> >>
> That's related to process dispatch time in the kernel. It might>>
> > be the>> >> >> > case that this expectation is a bit
aggressive (mea culpa).>> >> >> >>> >>
> > > In the mean time, as long as those timings remain close to the>> >> >> > \
> > > expectations (60 vs 50ms) I'd ignore them.>> >> >> >>> >> >> > Those messages
are meant to debug real-time problems - which you>> >> don't>> >> >> > appear to be \
having.>> >> >>
> > > > > > > > -- Alan Robertson>> >>
> > > alanr@unix.sh>> >> >> >>> >>
> > > > > > > > > > On 05/12/2011 12:54 PM,
gilmarlinux@agrovale.com.br wrote:>> >> >> >> Hello!>> >> >> >> I'm using heartbeat \
version 3.0.3-2 on debian squeeze with>> dedicated>> >> >> >> gigabit
ethernet interface for the heartbeat.>> >> >> >> But even
this generates the following message:>> >> >> >> WARN:
Gmain_timeout_dispatch: Dispatch function for send local>> >>
status>> >> >> >> took too long to execute: 60 ms (> 50
ms) (GSource: 0x101c350)>> >> >> >> I'm using eth1 to eth2
and to Synchronize DRBD(eth1) HEARBEAT>> >> (eth2).>>
> > > > > > I tried increasing the values deadtime = 20 and 15
warntime>> >> >> >> Interface Gigabit Ethernet controller:
Intel Corporation 82575GB>> >> >> >> Serv.1 and the
Ethernet controller: Broadcom Corporation>> >> NetXtreme II>> >> >> >> BCM5709 in \
Serv.2>> >> >>
> > Tested using two Broadcom for the heartbeat, also without>>
success.>> >> >> >>>> >> >>
> > Thanks>> >> >> >>> >> >>
> -->> >> >>>> >>>> >>>> >> _______________________________________________________>> \
> >> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org>> >>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev>> >> Home
Page: http://linux-ha.org/>> >>> >
_______________________________________________________>> > Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org>> >
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev>> > Home Page:
http://linux-ha.org/>> >>>>>>>
_______________________________________________________>> Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org>>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev>> Home Page:
http://linux-ha.org/> > > --> Alan
Robertson<alanr@unix.sh>> > "Openness is the foundation and
preservative of friendship... Let me claim from you at> all times your
undisguised opinions." - William Wilberforce> >
_______________________________________________________> Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev> Home Page:
http://linux-ha.org/>
[Attachment #5 (text/html)]
<div align="left"><span lang="en" class="long_text" id="result_box"><span class="hps"
title="Clique para mostrar traduções alternativas">Ok</span><span title="Clique para
mostrar traduções alternativas" class="">,<br />Thank you</span><span title="Clique para
mostrar traduções alternativas" class="">.</span><br /> <span class="hps" title="Clique
para mostrar traduções alternativas">I'm</span> <span class="hps" title="Clique para
mostrar traduções alternativas">trying to</span> <span class="hps" title="Clique para
mostrar traduções alternativas">isolate the</span> <span class="hps" title="Clique para
mostrar traduções alternativas">problem</span> <span class="hps" title="Clique para
mostrar traduções alternativas">to the</span> <span class="hps" title="Clique para
mostrar traduções alternativas">maximum</span><span title="Clique para mostrar traduções
alternativas" class="">,</span> <span class="hps" title="Clique para mostrar traduções
alternativas">so</span> <span class="hps" title="Clique para mostrar traduções
alternativas">I try to</span> <span class="hps" title="Clique para mostrar traduções
alternativas">diagnose</span> <span class="hps" title="Clique para mostrar traduções
alternativas">the problem.</span> <span class="hps" title="Clique para mostrar traduções
alternativas"><br />I've tried</span> <span class="hps" title="Clique para mostrar
traduções alternativas">tools</span> <span class="hps" title="Clique para mostrar
traduções alternativas">like</span> <span class="hps" title="Clique para mostrar
traduções alternativas">sar</span> <span class="hps" title="Clique para mostrar
traduções alternativas">iostat</span> <span class="hps" title="Clique para mostrar
traduções alternativas">to check</span> <span class="hps" title="Clique para mostrar
traduções alternativas">the</span> <span class="hps" title="Clique para mostrar
traduções alternativas">system queries.</span> <span class="hps" title="Clique para
mostrar traduções alternativas"><br />But</span> <span class="hps" title="Clique para
mostrar traduções alternativas">for</span> <span class="hps" title="Clique para mostrar
traduções alternativas">now everything</span> <span class="hps" title="Clique para
mostrar traduções alternativas">without</span> <span class="hps" title="Clique para
mostrar traduções alternativas">problems</span></span></div>
<br />> That's probably OK. If you're really having a problem, it should<br />>
ordinarily show it up before it causes a false failover.<br />> <br />> Then you
can figure out if you want to raise your timeout or figure out<br />> what's causing
the slow processing.<br />> <br />> <br />> On 05/14/2011 09:08 AM,
gilmarlinux@agrovale.com.br wrote:<br />>> Thanks again.<br />>> deadtime 30
and warntime 15 this good ?<br />>><br />>> > BUT also either make
warntime smaller or deadtime larger...<br />>> ><br />>> ><br
/>>> > On 5/13/2011 7:48 PM, gilmarlinux@agrovale.com.br wrote:<br />>>
>> Thank you for your attention.<br />>> >> His recommendation and
wait, if only to continue the logs I get<br />>> >> following warning if the
services do not migrate to another server<br />>> >> just keep watching the
logs warning.<br />>> >><br />>> >> > I typically make
deadtime something like 3 times warntime. That way<br />>> >> > you'll
get data before you get into trouble. When your heartbeats<br />>> >> >
exceed warntime, you get information on how late it is. I would<br />>> >>
> typically make deadtime AT LEAST twice the latest time you've<br />>> ever
seen<br />>> >> > with warntime.<br />>> >> ><br
/>>> >> > If the worst case you ever saw was this 60ms instead of 50ms,
I'd<br />>> look<br />>> >> > somewhere else for the problem.
However, it is possible that you<br />>> have a<br />>> >> >
hardware trouble, or a kernel bug. Possible, but unlikely.<br />>> >>
><br />>> >> > More logs are always good when looking at a problem
like this.<br />>> >> > hb_report will get you lots of logs and so on for
the next time it<br />>> >> happens.<br />>> >> ><br
/>>> >> > On 05/13/2011 11:44 AM, gilmarlinux@agrovale.com.br wrote:<br
/>>> >> >> Thanks for the help.<br />>> >> >><br
/>>> >> >> I had a problem the 30 days that began with this post, and
after two<br />>> >> >> days the heartbeat message that the accused
had fallen server1 and<br />>> >> >> services migrated to server2<br
/>>> >> >> Now with this change to eth1 and eth2 for drbd and
heartbeat to the<br />>> >> >> amendment of warntime deadtime 20 to 15
and do not know if this will<br />>> >> >> happen again.<br />>>
>> >> Thanks<br />>> >> >><br />>> >> >>
> That's related to process dispatch time in the kernel. It might<br />>>
>> be the<br />>> >> >> > case that this expectation is a bit
aggressive (mea culpa).<br />>> >> >> ><br />>> >>
>> > In the mean time, as long as those timings remain close to the<br
/>>> >> >> > expectations (60 vs 50ms) I'd ignore them.<br
/>>> >> >> ><br />>> >> >> > Those messages
are meant to debug real-time problems - which you<br />>> >> don't<br
/>>> >> >> > appear to be having.<br />>> >> >>
><br />>> >> >> > -- Alan Robertson<br />>> >>
>> > alanr@unix.sh<br />>> >> >> ><br />>> >>
>> ><br />>> >> >> > On 05/12/2011 12:54 PM,
gilmarlinux@agrovale.com.br wrote:<br />>> >> >> >> Hello!<br
/>>> >> >> >> I'm using heartbeat version 3.0.3-2 on debian
squeeze with<br />>> dedicated<br />>> >> >> >> gigabit
ethernet interface for the heartbeat.<br />>> >> >> >> But even
this generates the following message:<br />>> >> >> >> WARN:
Gmain_timeout_dispatch: Dispatch function for send local<br />>> >>
status<br />>> >> >> >> took too long to execute: 60 ms (> 50
ms) (GSource: 0x101c350)<br />>> >> >> >> I'm using eth1 to eth2
and to Synchronize DRBD(eth1) HEARBEAT<br />>> >> (eth2).<br />>>
>> >> >> I tried increasing the values deadtime = 20 and 15
warntime<br />>> >> >> >> Interface Gigabit Ethernet controller:
Intel Corporation 82575GB<br />>> >> >> >> Serv.1 and the
Ethernet controller: Broadcom Corporation<br />>> >> NetXtreme II<br
/>>> >> >> >> BCM5709 in Serv.2<br />>> >> >>
>> Tested using two Broadcom for the heartbeat, also without<br />>>
success.<br />>> >> >> >><br />>> >> >>
>> Thanks<br />>> >> >> ><br />>> >> >>
> --<br />>> >> >><br />>> >><br />>> >><br
/>>> >> _______________________________________________________<br
/>>> >> Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org<br />>> >>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev<br />>> >> Home
Page: http://linux-ha.org/<br />>> ><br />>> >
_______________________________________________________<br />>> > Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org<br />>> >
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev<br />>> > Home Page:
http://linux-ha.org/<br />>> ><br />>><br />>><br />>>
_______________________________________________________<br />>> Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org<br />>>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev<br />>> Home Page:
http://linux-ha.org/<br />> <br />> <br />> --<br />> Alan
Robertson<alanr@unix.sh><br />> <br />> "Openness is the foundation and
preservative of friendship... Let me claim from you at<br />> all times your
undisguised opinions." - William Wilberforce<br />> <br />>
_______________________________________________________<br />> Linux-HA-Dev:
Linux-HA-Dev@lists.linux-ha.org<br />>
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev<br />> Home Page:
http://linux-ha.org/<br />>
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic