Re: Problem Xen 4.0-amd64 + Heartbeat 3.0.3-2 with Debian Squeeze

[Ian Campbell <Ian.Campbell@citrix.com>]

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@agrovale.com.br 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.