On Tue, 17 Dec 2013 09:28:51 +0100
Michael Schwartzkopff m...@sys4.de wrote:
Am Dienstag, 17. Dezember 2013, 09:17:31 schrieb ma...@nucleus.it:
Hi to all,
i set up a 2 node cluster with a cross cable between the two nodes
without stonith ; i know this is not the best way but this is the
Hi David,
2013/12/18 David Vossel dvos...@redhat.com:
That's a really weird one... I don't see how it is possible for op-id to be
NULL there. You might need to give valgrind a shot to detect whatever is
really going on here.
-- Vossel
Thank you for advice. I try it.
Kazunori INOUE
Hi,
When I set only migration-limit without setting node-action-limit in
pacemaker-1.1,
the number of 'operation' other than migrate_to/from was limited to
the value of migration-limit.
(The node that I used has 8 cores.)
[cib]
property \
no-quorum-policy=freeze \
stonith-enabled=true \
Hi, Andrew and ALL.
I'm sorry, but I again found an error. :)
Crux of the problem:
# crm_attribute --type crm_config --attr-name stonith-enabled --query; echo $?
scope=crm_config name=stonith-enabled value=true
0
# crm_attribute --type crm_config --attr-name stonith-enabled --update firstval
Hi !
I'm currently building a 2 node cluster for firewalling.
I would like to run a shorewall on both on the master and the Slave
node. I tried many things but nothing works as expected. Shorewall
configurations are good.
What I want to do is to start shorewall standby on the other node as
soon
Dear all,
It is maybe a stupid question... Sorry I'm a new user of pacemaker.
I have 2 nodes and 5 resources (resource1, resource2, resource3, resource4 and
resource5). The 5 resources have to work together on the same node.
I tried the feature group and colocation .. but I have always the same
Le 18/12/2013 17:20, Brusq, Jerome a écrit :
Dear all,
It is maybe a stupid question… Sorry I’m a new user of pacemaker.
Not at all.
I have 2 nodes and 5 resources (resource1, resource2, resource3,
resource4 and resource5). The 5 resources have to work together on the
same node.
I tried
Dear all,
I have a custom lsb script that launch a custom process.
primitive myscript lsb:ha_swift \
op start interval=0 timeout=30s \
op stop interval=0 timeout=30s \
op monitor interval=15s on-fail=restart \
When this one crashes, I have the feeling that pacemaker do :
- Original Message -
From: David Vossel dvos...@redhat.com
To: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Sent: Wednesday, December 11, 2013 3:33:46 PM
Subject: Re: [Pacemaker] Time to get ready for 1.1.11
- Original Message -
From: Andrew
On 19 Dec 2013, at 4:03 am, Brusq, Jerome jerome.br...@signalis.com wrote:
Dear all,
I have a custom lsb script that launch a custom process.
primitive myscript lsb:ha_swift \
op start interval=0 timeout=30s \
op stop interval=0 timeout=30s \
op monitor interval=15s
On 14 Dec 2013, at 7:51 am, Stephane Robin sro...@kivasystems.com wrote:
Hi,
I'm trying to build Pacemaker-1.1.10 (from git), with corosync 2.3.2 and
libqb 0.16.0 on a CentOS 5.10 64b system.
I have latest auto tools (automake 1.14, autoconf 2.69, lib tool 2.4,
pkg-config 0.27.1)
18.12.2013 23:21, Rainer Brestan wrote:
Hi Lars,
maybe a little off topic.
What i really miss in crmsh is the possibility to specify resource
parameters which are different on different nodes, so the parameter is
node dependant.
In XML syntax this is existing, Andrew gave me the hint as
On 19/12/13 12:44 AM, Nikita Staroverov wrote:
Hello!
Some months ago i wrote about manual fence confirmation by stonith_admin
-C. Andrew fixed this, but it works only for pacemaker+corosync.
CMAN-based configuration won't do manual fencing this way.
I tried stonith_admin -C , pacemaker made
Re-sending to keep this in the public archives. Please keep replies on
the list, it benefits everyone that way.
On 19/12/13 01:17 AM, Nikita Staroverov wrote:
Some months ago i wrote about manual fence confirmation by stonith_admin
-C. Andrew fixed this, but it works only for
Hi David,
2013/12/19 David Vossel dvos...@redhat.com:
- Original Message -
From: Kazunori INOUE kazunori.ino...@gmail.com
To: pm pacemaker@oss.clusterlabs.org
Sent: Wednesday, December 18, 2013 4:56:20 AM
Subject: [Pacemaker] Question about behavior of the post-failure during the
Please see:
https://access.redhat.com/site/articles/36302
If you don't have an account, the relevant part is:
Usage of fence_manual is not supported in any production cluster. You
may use this fence agent for development or debugging purposes only.
I wrote about fence_ack_manual, not
16 matches
Mail list logo