Hello Serge,
Thank you so much for your quick action!
I'll test the patch.
Regards,
Yoshihiko SATO.
Attached is a patch that checks that DomU disappears from the xm
list on Dom0 after running destroy.
On Mon, Apr 13, 2009 at 10:03 PM, Serge Dubrouski serge...@gmail.com wrote:
Hello -
This
On Wed, Apr 15, 2009 at 06:13, devi d...@atc.tcs.com wrote:
This is because, my resources are virtual machines on 2 nodes. hence ip
will be different, so inorder to specify them as resources in
haresources. Hence the cib.xml differs
No, it doesn't.
See the section Using Rules to Control
Just one email is fine thanks... no need to send it 3 times.
You can probably achieve this with a couple of MailTo resources
2009/4/14 �^�I jzone...@gmail.com:
How can heartbeat notify me, if one node dead? Can I config it to send an
email to me? If can, how to do?
Ciao Dejan,
I am doing back forth on this item :-)
I moved to 2.14. version and back to V1 style... I don't use anymore
DRBD, just the mount
So the haresources file is the follows
afsitfs3.roma1.infn.it IPaddr::141.108.26.31/24/eth0
afsitfs3.roma1.infn.it
Ciao,
On Wed, Apr 15, 2009 at 12:53:41PM +0200, Cristina Bulfon wrote:
Ciao Dejan,
I am doing back forth on this item :-)
I moved to 2.14. version and back to V1 style... I don't use anymore DRBD,
just the mount
Do you need drbd?
So the haresources file is the follows
On Apr 15, 2009, at 1:18 PM, Dejan Muhamedagic wrote:
Ciao,
On Wed, Apr 15, 2009 at 12:53:41PM +0200, Cristina Bulfon wrote:
Ciao Dejan,
I am doing back forth on this item :-)
I moved to 2.14. version and back to V1 style... I don't use
anymore DRBD,
just the mount
Do you need drbd?
Hi all,
I decided to use the hb_gui to manage my nodes.
But the mgmtd refuses to be launched.
I used a strace to see what happened :
connect(4, {sa_family=AF_FILE, path=/var/run/heartbeat/register}, 110) = 0
getsockopt(4, SOL_SOCKET, SO_PEERCRED, o\24\0\0\0\0\0\0\0\0\0\0, [12]) = 0
recv(4,
Am Mittwoch, 15. April 2009 14:34:50 schrieb David Dumortier:
Hi all,
I decided to use the hb_gui to manage my nodes.
But the mgmtd refuses to be launched.
I used a strace to see what happened :
connect(4, {sa_family=AF_FILE, path=/var/run/heartbeat/register}, 110) =
0 getsockopt(4,
Ciao,
On Wed, Apr 15, 2009 at 01:37:40PM +0200, Cristina Bulfon wrote:
On Apr 15, 2009, at 1:18 PM, Dejan Muhamedagic wrote:
Ciao,
On Wed, Apr 15, 2009 at 12:53:41PM +0200, Cristina Bulfon wrote:
Ciao Dejan,
I am doing back forth on this item :-)
I moved to 2.14. version and back to V1
Hi,
On Tue, Apr 14, 2009 at 01:14:08PM +, Chris Picton wrote:
Hi all
I am using heartbeat 2.1.4, and have an issue where a few resources got
to a state where they could not run anywhere.
I found that stopping, deleting the resource, and then running
crm_resource -C -r $resource -H
Hi and thanks for the response,
Michael Schwartzkopff a écrit :
Upgrade to a recent version. heartbeat 2.99 and pacemaker 1.0.3.
Target servers are production servers. Beta is not an option for me.
Perhaps I missed something. Is there a need of cib.xml or the GUI will
create it ?
--
Dr.
Am Mittwoch, 15. April 2009 15:20:40 schrieb David Dumortier:
Hi and thanks for the response,
Michael Schwartzkopff a écrit :
Upgrade to a recent version. heartbeat 2.99 and pacemaker 1.0.3.
Target servers are production servers. Beta is not an option for me.
Perhaps I missed something. Is
Hi,
On Tue, Apr 14, 2009 at 05:03:55PM +0200, David Dumortier wrote:
Hi the list,
I have to setup an heartbeat on a 2 computers-cluster with PostGreSQL. I
setuped a fail-over on PG with a warm-stanby : a file flag tell the slave
to take the master state.
There is a RA for postgres (pgsql).
On Wed, Apr 15, 2009 at 15:20, David Dumortier
david.dumort...@linagora.com wrote:
Hi and thanks for the response,
Michael Schwartzkopff a écrit :
Upgrade to a recent version. heartbeat 2.99 and pacemaker 1.0.3.
Target servers are production servers. Beta is not an option for me.
Neither
On Fri, Apr 10, 2009 at 14:03, Dejan Muhamedagic deja...@fastmail.fm wrote:
Hi,
On Fri, Apr 10, 2009 at 01:59:29AM -0400, Martin Suehowicz wrote:
I ran in to an issue tonight where I could not delete or shutdown the
R_192.168.1.2 the resource below. I was running service heartbeat stop.
It
Ciao,
it seems to be solved:
it was my fault ,try to mount xfs filesystem instead of ext3 ..correct
the typo and did the filesystem check.
Everything seems working I don't get the error umount .. busy but
when I tried to simulate the down of the active node and switch to the
passive ..
Hi list,
is there anybody running 2.1.4 on CentOS (5)? Recent rpms are 2.1.3-3
AFAICS.
Thanks for any hint,
Timo :)
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also:
Am Mittwoch, 15. April 2009 15:59:54 schrieb Timo Schoeler:
Hi list,
is there anybody running 2.1.4 on CentOS (5)? Recent rpms are 2.1.3-3
AFAICS.
Thanks for any hint,
Timo :)
Use 2.1.4 or pacemaker 1.0.3. It causes less headache.
--
Dr. Michael Schwartzkopff
MultiNET Services GmbH
Hi list,
is there anybody running 2.1.4 on CentOS (5)? Recent rpms are 2.1.3-3
AFAICS.
Thanks for any hint,
Timo :)
Use 2.1.4 or pacemaker 1.0.3. It causes less headache.
Sure, that's what the tenor's here as well as what the changelogs say...
I'm just hesitating because there's no
Andrew Beekhof writes:
You can't. There should be a shutdown escalation after 5 minutes
if something hangs resourcewise.
Actually the default is 10 minutes.
how to reduce it?
-- juha
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
I'm running 2.1.4 on CentOS 5.2. They aren't the packages I'm currently using
but it appears that the EPEL repository packages 2.1.4 for CentOS 5.2 as well.
Should be easy enough to exclude heartbeat from extras and install it from EPEL.
--Ryan
Timo Schoeler wrote:
Hi list,
is there anybody
Am Mittwoch, 15. April 2009 16:29:23 schrieb Timo Schoeler:
Hi list,
is there anybody running 2.1.4 on CentOS (5)? Recent rpms are 2.1.3-3
AFAICS.
Thanks for any hint,
Timo :)
Use 2.1.4 or pacemaker 1.0.3. It causes less headache.
Sure, that's what the tenor's here as well as
set the shutdown_escalation cluster option
On Wed, Apr 15, 2009 at 16:05, Juha Heinanen j...@tutpro.com wrote:
Andrew Beekhof writes:
You can't. There should be a shutdown escalation after 5 minutes
if something hangs resourcewise.
Actually the default is 10 minutes.
how to
On Tue, Apr 14, 2009 at 9:44 AM, Jiann-Ming Su sujiannm...@gmail.com wrote:
Yep, that's what mine looks like. It's installed with the same custom
rpm package that I've used on our other Linux HA clusters (12 systems
total). It's only affecting this one cluster member. The other two
systems
Hi,
I think I can use hb_delnode when I want to remove one node from the
cluster,
Should I do hb_delnode on DC?
Is there any distinction between DC or not to do that?
Thanks,
Junko
-Original Message-
From: linux-ha-boun...@lists.linux-ha.org
thus Michael Schwartzkopff spake:
Am Mittwoch, 15. April 2009 16:29:23 schrieb Timo Schoeler:
Hi list,
is there anybody running 2.1.4 on CentOS (5)? Recent rpms are 2.1.3-3
AFAICS.
Thanks for any hint,
Timo :)
Use 2.1.4 or pacemaker 1.0.3. It causes less headache.
Sure, that's what the
On Thu, Apr 16, 2009 at 03:41, Junko IKEDA ike...@intellilink.co.jp wrote:
Hi,
I think I can use hb_delnode when I want to remove one node from the
cluster,
Should I do hb_delnode on DC?
Is there any distinction between DC or not to do that?
Nope.
Hi List,
I am new to linux-ha and this is my first attempt at it.
My configuration:
1. OS = Redhat Enterprise Linux 5.x
2. HA = v2.1.3-3 RPM install (using CentoS repository rpms)
I am having trouble coming up with a clean cib.xml (see attachment).
I want to implement a HA solution to
28 matches
Mail list logo
