WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem Xen 4.0-amd64 + Heartbeat 3.0.3-2 with Debian S

To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Problem Xen 4.0-amd64 + Heartbeat 3.0.3-2 with Debian Squeeze
From: gilmarlinux@xxxxxxxxxxxxxxx
Date: Mon, 30 May 2011 08:18:11 -0300 (BRT)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "gilmarlinux@xxxxxxxxxxxxxxx" <gilmarlinux@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 30 May 2011 06:57:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <1306577527.23577.22.camel@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <56480.201.34.53.103.1306542323.squirrel@xxxxxxxxxxxxxxxxxxxx> <1306577527.23577.22.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.5
Ok, Thanks.
I thought it might be something I / O xen causing this in heartbeat.


> I saw your previous message and to be honest it wasn't clear if you were
> asking for help with an issue or providing a solution you had
> discovered.
>
> Since you have repeated it I assume the former. If you don't initially
> get a response to a mail then simply repeating it verbatim in a new
> thread may not help (and can be considered rude) -- you should consider
> why people may not have responded. i.e. whether the mail needs
> clarifying or additional information etc.
>
> Anyway, this seems like an issue with heartbeat, perhaps you should ask
> for help on the heartbeat mailing list, since there you are more likely
> to find experts in that field there. In terms of Xen I think this
> question would have been better suited to xen-users@ in the first
> instance.
>
> Ian.
>
> On Sat, 2011-05-28 at 01:25 +0100, gilmarlinux@xxxxxxxxxxxxxxx wrote:
>> Hi!
>> Hello! Can know. I have the solution Xen 4.0 amd64 + Heartbeat 3.0.3-2
>> on
Debian Squeeze installed using apt-get. I have the eth1 and eth2
>> used by DRBD Heartbeat and used by the other three interfaces used by
>> the domus as a bridge. The log of the heartbeat is generating this
>> message:
>>
>> May 25 08:23:28 inga heartbeat: [26789]: WARN: Gmain_timeout_dispatch:
>> Dispatch function for send local status took too long to execute: 310
>> ms (> 50 ms) (GSource: 0x1dae330)
>> May 25 08:28:26 inga heartbeat: [26789]: WARN: Gmain_timeout_dispatch:
>> Dispatch function for send local status took too long to execute: 90
>> ms (> 50 ms) (GSource: 0x1dae330)
>>
>> A few more days and had this message and then migrated to the server1
>> to server2 domus.
>> I changed the values ​​of ha.cf as below.
>> deadtime 30
>> warntime 15.
>>
>> The Server1 (dom0) 8 domU , already Server2 (dom0) has 3 domU.
>>
>> Configuration Servers dom0
>>
>> 2 Processor Quad Core 2.4
>> 32 GB ram
>> 6 Gigabit Ethernet
>> 5 HD SAS 300 GB 15 K raid 5
>> Thanks.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel