Hi,
I am using corosync.1.2.1. I want to upgrade corosync from 1.2 to
1.4.2.
please can you let me know which version of cluster-glue and pacemekr
are compatiable with corosync1.4.2
Currentely with corosync1.4.2 I am using pacemaker 1.0.10 and
cluster-glue1.0.3 and I am getting
Hello Andreas,
Thanks for the reply.
So can you please suggest what Stonith plugin should I use for the
production release of my software. I have the following system requirements:
1. If a node in the cluster fails, it should be reboot and resources should
re-start on the node.
2. If the
Hello,
Minor updates in the first requirement.
1. If a resource fails, node should reboot (through fencing mechanism) and
resources should re-start on the node.
2. If the physical link between the nodes in a cluster fails then that node
should be isolated (kind of a power down) and the resources
Hi,
Can you please share the link for the download, as I am not able to found the
pacemaker version 1.1.7 on Git.
Following is the link for the pacemaker version I am checking on -
https://github.com/ClusterLabs/pacemaker
Not sure if that is correct, since I am using Git 1st time.
Request you
Hello,
On 10/18/2011 09:00 AM, neha chatrath wrote:
Hello,
Minor updates in the first requirement.
1. If a resource fails, node should reboot (through fencing mechanism)
and resources should re-start on the node.
Why would you want that? This would increase the service downtime
Hello,
On 10/18/2011 08:11 AM, manish.gu...@ionidea.com wrote:
Hi,
I am using corosync.1.2.1. I want to upgrade corosync from 1.2 to
1.4.2.
please can you let me know which version of cluster-glue and pacemekr
are compatiable with corosync1.4.2
Currentely with
Hello,
1. If a resource fails, node should reboot (through fencing mechanism)
and resources should re-start on the node.
Why would you want that? This would increase the service downtime
considerable. Why is a local restart not possible ... and even if there
is a good reason for a reboot, why
On Mon, Oct 17, 2011 at 7:14 PM, Trevor Hemsley thems...@voiceflex.com wrote:
Andrew Beekhof wrote:
On Sat, Oct 15, 2011 at 1:46 AM, Trevor Hemsley thems...@voiceflex.com
wrote:
Hi
I've just built pacemaker 1.1.6 on CentOS 5.7 with the aid of the
attached
patches. Not sure if the
I have a pacemaker 1.0.10 installation on rhel5 but I can't seem to
manage to get a working stonith configuration. I have tested my stonith
device manually using the stonith command and it works fine. What
doesn't seem to be happening is pacemaker/stonithd actually asking for a
stonith. In my
Hello,
On 10/18/2011 02:59 PM, Brian J. Murrell wrote:
I have a pacemaker 1.0.10 installation on rhel5 but I can't seem to
manage to get a working stonith configuration. I have tested my stonith
device manually using the stonith command and it works fine. What
doesn't seem to be happening
On 10/18/2011 11:21 AM, neha chatrath wrote:
Hello,
1. If a resource fails, node should reboot (through fencing mechanism)
and resources should re-start on the node.
Why would you want that? This would increase the service downtime
considerable. Why is a local restart not possible ... and
On 11-10-18 09:40 AM, Andreas Kurz wrote:
Hello,
Hi,
I'd expect this to be the problem ... if you insist on using an
unsymmetric cluster you must add a location score for each resource you
want to be up on a node ... so add a location constraint for the fencing
clone for each node ... or
Hello all, I'm having some problems getting resources to fail over
properly I need the IP's to swith to a different node when it cannot
ping. We're doing a shut on the respective interfaces to simulate
cables being unplugged but I keep getting exec timeouts and unknown
errors.
crm_mon -fortA
On 2011-10-18 19:38, James Horsfall (CTR) wrote:
Hello all, I’m having some problems getting resources to fail over
properly I need the IP’s to swith to a different node when itcannotping.
We’re doing a“shut”on the respective interfaces to simulate cables
beingunpluggedbut I keep getting exec
http://pastebin.com/VMx2mN4f
Posted here thanks!
-Original Message-
From: Florian Haas [mailto:flor...@hastexo.com]
Sent: Tuesday, October 18, 2011 3:07 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Exec Failure issues.
On 2011-10-18 19:38, James Horsfall (CTR)
On 2011-10-18 19:38, James Horsfall (CTR) wrote:
Hello all, I’m having some problems getting resources to fail over
properly I need the IP’s to swith to a different node when it cannot ping.
We’re doing a “shut” on the respective interfaces to simulate cables
being unplugged but I keep getting
thank you
Andreas
Now I am facing core dump issue with
corosync-1.4.2
cluster-glue-1.0.7
pacemaker-1.0.11
In many scenario I getting core dump during corosync start operation for 2
rings like.
1. Configure 2 rings ring0 10.16.16.0, ring1 192.168.1.0
ring1 network(ifconfig eth1 192.168.1.14
17 matches
Mail list logo