Re: [ClusterLabs] Change disk

On 09/14/2016 09:30 AM, NetLink wrote: > My two node email server cluster uses corosync 1.4.2. > > The device /dev/drbd3, which only holds the email data in a separated > disk, is running out of space. > > To change the two disks for bigger ones I’m thinking to use the > following strategy: > >

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/22/2016 05:58 PM, Andrew Beekhof wrote: > > > On Fri, Sep 23, 2016 at 1:58 AM, Ken Gaillot <kgail...@redhat.com > <mailto:kgail...@redhat.com>> wrote: > > On 09/22/2016 09:53 AM, Jan Pokorný wrote: > > On 22/09/16 08:42 +0200, Kristoffer Grönlun

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 10/02/2016 10:02 PM, Andrew Beekhof wrote: >> Take a >> look at all of nagios' options for deciding when a failure becomes "real". > > I used to take a very hard line on this: if you don't want the cluster > to do anything about an error, don't tell us about it. > However I'm slowly changing

Re: [ClusterLabs] stonithd/fenced filling up logs

On 10/04/2016 11:31 AM, Israel Brewster wrote: > I sent this a week ago, but never got a response, so I'm sending it > again in the hopes that it just slipped through the cracks. It seems to > me that this should just be a simple mis-configuration on my part > causing the issue, but I suppose it

Re: [ClusterLabs] stonithd/fenced filling up logs

@alteeve.ca >>> <mailto:li...@alteeve.ca>> wrote: >>>> >>>> On 04/10/16 07:09 PM, Israel Brewster wrote: >>>>> On Oct 4, 2016, at 3:03 PM, Digimer <li...@alteeve.ca >>>>> <mailto:li...@alteeve.ca>> wrote: >>>>&

Re: [ClusterLabs] No DRBD resource promoted to master in Active/Passive setup

a...@cgi.com > Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter > de.cgi.com/pflichtangaben. > > CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI > Group Inc. and its affiliates may be contained in this message. If you are >

Re: [ClusterLabs] best practice fencing with ipmi in 2node-setups / cloneresource/monitor/timeout

On 09/21/2016 01:51 AM, Stefan Bauer wrote: > Hi Ken, > > let met sum it up: > > Pacemaker in recent versions is smart enough to run (trigger, execute) the > fence operation on the node, that is not the target. > > If i have an external stonith device that can fence multiple nodes, a single >

Re: [ClusterLabs] kind=Optional order constraint not working at startup

On 09/21/2016 09:00 AM, Auer, Jens wrote: > Hi, > > could this be issue 5039 (http://bugs.clusterlabs.org/show_bug.cgi?id=5039)? > It sounds similar. Correct -- "Optional" means honor the constraint only if both resources are starting *in the same transition*. shared_fs has to wait for the

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/21/2016 02:23 AM, Kristoffer Grönlund wrote: > First of all, is there a use case for when fence-after-3-failures is a > useful behavior? I seem to recall some case where someone expected that > to be the behavior and were surprised by how pacemaker works, but that > problem wouldn't be

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/20/2016 07:51 PM, Andrew Beekhof wrote: > > > On Wed, Sep 21, 2016 at 6:25 AM, Ken Gaillot <kgail...@redhat.com > <mailto:kgail...@redhat.com>> wrote: > > Hi everybody, > > Currently, Pacemaker's on-fail property allows you to configure how t

Re: [ClusterLabs] Virtual ip resource restarted on node with down network device

On 09/19/2016 10:04 AM, Jan Pokorný wrote: > On 19/09/16 10:18 +, Auer, Jens wrote: >> Ok, after reading the log files again I found >> >> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: Initiating action 3: stop >> mda-ip_stop_0 on MDA1PFP-PCS01 (local) >> Sep 19 10:03:45 MDA1PFP-S01

Re: [ClusterLabs] No DRBD resource promoted to master in Active/Passive setup

think for any reason that > this message may have been addressed to you in error, you may not use or copy > or deliver this message to anyone else. In such case, you should destroy this > message and are asked to notify the sender by reply e-mail. > > ___

Re: [ClusterLabs] [Linux-ha-dev] Announcing crmsh release 2.1.7

On 09/23/2016 06:59 AM, Kostiantyn Ponomarenko wrote: >>> Out of curiosity: What do you use it for, where the two_node option > is not sufficient? > > Alongside with starting the cluster with two nodes I need that > possibility of starting the cluster with only one node. > "two_node" option

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/22/2016 09:53 AM, Jan Pokorný wrote: > On 22/09/16 08:42 +0200, Kristoffer Grönlund wrote: >> Ken Gaillot <kgail...@redhat.com> writes: >> >>> I'm not saying it's a bad idea, just that it's more complicated than it >>> first sounds, so it's

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/22/2016 10:43 AM, Jan Pokorný wrote: > On 21/09/16 10:51 +1000, Andrew Beekhof wrote: >> On Wed, Sep 21, 2016 at 6:25 AM, Ken Gaillot <kgail...@redhat.com> wrote: >>> Our first proposed approach would add a new hard-fail-threshold >>> operation property. If s

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/22/2016 12:58 PM, Kristoffer Grönlund wrote: > Ken Gaillot <kgail...@redhat.com> writes: >> >> "restart" is the only on-fail value that it makes sense to escalate. >> >> block/stop/fence/standby are final. Block means "don't touch the &

Re: [ClusterLabs] best practice fencing with ipmi in 2node-setups / cloneresource/monitor/timeout

On 09/20/2016 06:42 AM, Digimer wrote: > On 20/09/16 06:59 AM, Stefan Bauer wrote: >> Hi, >> >> i run a 2 node cluster and want to be save in split-brain scenarios. For >> this i setup external/ipmi to stonith the other node. > > Please use 'fence_ipmilan'. I believe that the older external/ipmi

Re: [ClusterLabs] Virtual ip resource restarted on node with down network device

o you in error, you may not use or copy > or deliver this message to anyone else. In such case, you should destroy this > message and are asked to notify the sender by reply e-mail. > > > Von: Ken Gaillot [kgail...@redhat.com] > Gesendet:

Re: [ClusterLabs] Virtual ip resource restarted on node with down network device

On 09/16/2016 10:08 AM, Auer, Jens wrote: > Hi, > > I have configured an Active/Passive cluster to host a virtual ip > address. To test failovers, I shutdown the device the virtual ip is > attached to and expected that it moves to the other node. However, the > virtual ip is detected as FAILED,

Re: [ClusterLabs] Preferred location is sometimes ignored

On 09/16/2016 10:59 AM, Auer, Jens wrote: > On 09/16/2016 09:45 AM, Auer, Jens wrote: >>> Hi, >>> >>> MDA1PFP-S01 14:41:35 1805 0 ~ # pcs constraint --full >>> Location Constraints: >>> Resource: mda-ip >>> Enabled on: MDA1PFP-PCS01 (score:50) >>> (id:location-mda-ip-MDA1PFP-PCS01-50) >>>

Re: [ClusterLabs] DRBD failover in Pacemaker

On 09/06/2016 02:04 PM, Devin Ortner wrote: > I have a 2-node cluster running CentOS 6.8 and Pacemaker with DRBD. I have > been using the "Clusters from Scratch" documentation to create my cluster and > I am running into a problem where DRBD is not failing over to the other node > when one goes

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

On 08/22/2016 03:56 PM, Attila Megyeri wrote: > Hi Ken, > > Thanks a lot for your feedback, my answers are inline. > > > >> -Original Message----- >> From: Ken Gaillot [mailto:kgail...@redhat.com] >> Sent: Monday, August 22, 2016 4:12 PM >>

Re: [ClusterLabs] ocf::heartbeat:IPaddr

On 08/25/2016 10:51 AM, Gabriele Bulfon wrote: > Hi, > > I'm advancing with this monster cluster on XStreamOS/illumos ;) > > In the previous older tests I used heartbeat, and I had these lines to > take care of the swapping public IP addresses: > > primitive xstorage1_wan1_IP

[ClusterLabs] FYI: pacemaker will keep compatibility with python 2.6

by the next release, but we're making progress. As part of this work, I've developed our first official python coding guidelines. They are included in the "Pacemaker Development" source in the master branch. The online version hasn't been updated yet, but will be before the next release. -- K

Re: [ClusterLabs] pcs cluster auth returns authentication error

On 08/25/2016 03:04 PM, Jason A Ramsey wrote: > Please help. Just getting this thing stood up on a new set of servers > and getting stymied right out the gate: > > > > # pcs cluster auth node1 node2 > > Username: hacluster > > Password: > > > > I am **certain** that the password I’m

Re: [ClusterLabs] Howto restart resource

On 08/29/2016 01:38 AM, Stefano Ruberti wrote: > Dear all, > > I have following situation and I need an advice from you: > > in my Active/Passive Cluster (Ubuntu_16.04 corosync + pacemaker , no pcs) > > Node_ANode_B > Resource1Resource1 > Resource2Resource2 > Resource3

Re: [ClusterLabs] data loss of network would cause Pacemaker exit abnormally

On 08/27/2016 09:15 PM, chenhj wrote: > Hi all, > > When i use the following command to simulate data lost of network at one > member of my 3 nodes Pacemaker+Corosync cluster, > sometimes it cause Pacemaker on another node exit. > > tc qdisc add dev eth2 root netem loss 90% > > Is there any

Re: [ClusterLabs] ocf scripts shell and local variables

ttp://www.sonicle.com/> > *Music: *http://www.gabrielebulfon.com <http://www.gabrielebulfon.com/> > *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon > > > > -- > >

Re: [ClusterLabs] Failed to retrieve meta-data for custom ocf resource

On 09/28/2016 04:04 PM, Christopher Harvey wrote: > My corosync/pacemaker logs are seeing a bunch of messages like the > following: > > Sep 22 14:50:36 [1346] node-132-60 crmd: info: > action_synced_wait: Managed MsgBB-Active_meta-data_0 process 15613 > exited with rc=4 This is the

Re: [ClusterLabs] hi list

On 09/30/2016 10:10 AM, Антон Сацкий wrote: > so U mean that in fact IPaddr is IPaddr2 version > Is there a way to see that ip address was added except to see logs? > Before i can see ip using ifconfig > Regards and thanks for reply. "ip address show" (which can be abbreviated "ip a") See

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 09/28/2016 10:54 PM, Andrew Beekhof wrote: > On Sat, Sep 24, 2016 at 9:12 AM, Ken Gaillot <kgail...@redhat.com> wrote: >>> "Ignore" is theoretically possible to escalate, e.g. "ignore 3 failures >>> then migrate", but I can't think of

Re: [ClusterLabs] Pacemaker dependency fails when upgrading OS (Amazon Linux)

On 09/29/2016 05:30 PM, neeraj ch wrote: > Hello, > > I have pacemaker cluster running on Amazon Linux 2013.03 , details as > follows. > > OS : Amazon Linux 2013.03 64 bit (based off on el6) > Pacemaker version : 1.1.12 downloaded > form >

Re: [ClusterLabs] Colocation and ordering with live migration

On 10/10/2016 10:21 AM, Klaus Wenninger wrote: > On 10/10/2016 04:54 PM, Ken Gaillot wrote: >> On 10/10/2016 07:36 AM, Pavel Levshin wrote: >>> 10.10.2016 15:11, Klaus Wenninger: >>>> On 10/10/2016 02:00 PM, Pavel Levshin wrote: >>>>> 10.10.2016 14:

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On 11/07/2016 12:03 PM, Jehan-Guillaume de Rorthais wrote: > On Mon, 7 Nov 2016 09:31:20 -0600 > Ken Gaillot <kgail...@redhat.com> wrote: > >> On 11/07/2016 03:47 AM, Klaus Wenninger wrote: >>> On 11/07/2016 10:26 AM, Jehan-Guillaume de Rorthais wrote: >>

Re: [ClusterLabs] Preventing switchover in case of failing ping node

On 11/03/2016 08:49 AM, Detlef Gossrau wrote: > Hi all, > > is it possible to prevent a switchover in a active/passive cluster if a > ping node completely fails ? > > Situation: > > A ping node is put into maintenance and not reachable for a certain > time. The cluster nodes getting the

Re: [ClusterLabs] Live migration not working on shutdown

On 11/04/2016 05:51 AM, IT Nerb GmbH wrote: > Zitat von Klaus Wenninger <kwenn...@redhat.com>: > >> On 11/02/2016 06:32 PM, Ken Gaillot wrote: >>> On 10/26/2016 06:12 AM, Rainer Nerb wrote: >>>> Hello all, >>>> >>>> we're c

Re: [ClusterLabs] DRBD demote/promote not called - Why? How to fix?

On 11/04/2016 01:57 PM, CART Andreas wrote: > Hi > > I have a basic 2 node active/passive cluster with Pacemaker (1.1.14 , > pcs: 0.9.148) / CMAN (3.0.12.1) / Corosync (1.4.7) on RHEL 6.8. > This cluster runs NFS on top of DRBD (8.4.4). > > Basically the system is working on both nodes and I

Re: [ClusterLabs] pacemaker after upgrade from wheezy to jessie

e top of /var/lib/pacemaker/cib/cib.xml. Try >>> > changing the validate-with to pacemaker-next or pacemaker-1.2 and >>> see if >>> > you get better results. Don't edit the file directly though; use the >>> > cibadmin command so it signs the end result pr

Re: [ClusterLabs] Resources wont start on new node unless it is the only active node

On 11/08/2016 12:54 PM, Ryan Anstey wrote: > I've been running a ceph cluster with pacemaker for a few months now. > Everything has been working normally, but when I added a fourth node it > won't work like the others, even though their OS is the same and the > configs are all synced via salt. I

Re: [ClusterLabs] Antw: Resources wont start on new node unless it is the only active node

On 11/09/2016 02:33 AM, Ulrich Windl wrote: Ryan Anstey schrieb am 08.11.2016 um 19:54 in Nachricht >> Log when running cleaning up the resource on the OLD node: >> >> Nov 08 09:21:18 h3 crmd[11394]: warning: No match for shutdown action on >> 167838209 > > This

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On 11/07/2016 03:47 AM, Klaus Wenninger wrote: > On 11/07/2016 10:26 AM, Jehan-Guillaume de Rorthais wrote: >> On Mon, 7 Nov 2016 10:12:04 +0100 >> Klaus Wenninger <kwenn...@redhat.com> wrote: >> >>> On 11/07/2016 08:41 AM, Ulrich Windl wrote: >>>>

Re: [ClusterLabs] DRBD demote/promote not called - Why? How to fix?

(kind:Mandatory) > (id:order-NFSServer-NFS_global_clst-mandatory) > > start NFSServer then start BIND_global_clst (kind:Mandatory) > (id:order-NFSServer-BIND_global_clst-mandatory) > > Colocation Constraints: > > NFSServer with IPaddrNFS (score:INFINITY) > (id:

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On 11/04/2016 02:53 AM, Jan Pokorný wrote: > On 04/11/16 08:29 +0100, Ulrich Windl wrote: >> Ken Gaillot <kgail...@redhat.com> schrieb am 03.11.2016 um 17:08 in >> Nachricht <8af2ff98-05fd-a2c7-f670-58d0ff68e...@redhat.com>: >>> ClusterLabs is happy to

Re: [ClusterLabs] Migration-threshold, timeout and interval

On 10/19/2016 06:06 AM, Marcos Renato da Silva Junior wrote: > Hi, > > > It would be correct to say that both options have the same function : > > > meta migration-threshold="3" op monitor interval=10s > > op monitor interval=10 timeout=30 > > > If not what is the difference? You have two

Re: [ClusterLabs] Can't do anything right; how do I start over?

On 10/14/2016 02:48 PM, Jay Scott wrote: > I've been trying a lot of things from the introductory manual. > I have updated the instructions (on my hardcopy) to the versions > of corosync etc. that I'm using. I can't get hardly anything to > work reliably beyond the ClusterIP. > > So I start over

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

y on that resulting in a particular behavior. > -Regards > Nikhil > > On Mon, Oct 17, 2016 at 11:36 PM, Ken Gaillot <kgail...@redhat.com > <mailto:kgail...@redhat.com>> wrote: > > On 10/17/2016 09:55 AM, Nikhil Utane wrote: > > I see these

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

> notice: Stopcu_2(Redund_CU5_WB30) > notice: Movecu_3(Started Redun_CU4_Wb30 -> Redund_CU5_WB30) > > I have default stickiness set to 100 which is higher than any score > that I have configured. > I have migration_thre

Re: [ClusterLabs] set start-failure-is-fatal per resource?

On 10/17/2016 12:42 PM, Israel Brewster wrote: > I have one resource agent (redis, to be exact) that sometimes apparently > fails to start on the first attempt. In every case, simply running a > 'pcs resource cleanup' such that pacemaker tries to start it again > successfully starts the process.

Re: [ClusterLabs] DRBD Insufficient Privileges Error

On 11/20/2016 01:58 PM, Jasim Alam wrote: > Hi, > > > > I am trying to setup two node H/A cluster with DRBD. Following is my > configuration > > > > /[root@node-1 ~]# pcs config/ > > /Cluster Name: Cluster-1/ > > /Corosync Nodes:/ > > /node-1 node-2 / > > /Pacemaker Nodes:/ > >

Re: [ClusterLabs] Reliable check for "is starting" state of a resource

On 11/22/2016 10:53 AM, Kostiantyn Ponomarenko wrote: > Hi folks, > > I am looking for a good way of checking if a resource is in "starting" > state. > The thing is - I need to issue a command and I don't want to issue that > command when this particular resource is starting. This resource start

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

don't get how I can set this > timer. > Do I need to set this timer for each node? > > > Thank you, > Kostia > > On Mon, Nov 21, 2016 at 9:30 AM, Ulrich Windl > <ulrich.wi...@rz.uni-regensburg.de > <mailto:ulrich.wi...@rz.uni-regensburg.de>> wrote: >

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

se repeatedly changing the delay will make it useless (each delay change requires an immediate write). Having a separate command makes it less likely to be accidental. > > > Thank you, > Kostia > > On Mon, Nov 21, 2016 at 9:30 AM, Ulrich Windl > <ulrich.wi...@rz.uni-regens

Re: [ClusterLabs] Locate resource with functioning member of clone set?

On 11/22/2016 02:28 PM, Israel Brewster wrote: > On Nov 17, 2016, at 4:04 PM, Ken Gaillot <kgail...@redhat.com > <mailto:kgail...@redhat.com>> wrote: >> >> On 11/17/2016 11:37 AM, Israel Brewster wrote: >>> I have a resource that is set up as a clone set a

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

> wrote: > > Ken, > Thank you for the explanation. > I will try this low-level way of shadow cib creation tomorrow. > PS: I will sleep much better with this excellent news/idea. =) > > Thank you, > Kostia > > On Tue,

[ClusterLabs] Pacemaker 1.1.16 - Release Candidate 2

this as the final 1.1.16. Any feedback is appreciated. -- Ken Gaillot <kgail...@redhat.com> ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started

Re: [ClusterLabs] Q: late stop of dependency?

On 11/17/2016 02:46 AM, Ulrich Windl wrote: > Hi! > > I have a question: > When having dependencies like "A has to start before B" and "A has to start > before C". Now when shutting down, B and C are shut down before A, as > requested. > Now when B takes a long time to stop, C is stopped early.

Re: [ClusterLabs] Set a node attribute for multiple nodes with one command

On 11/18/2016 08:55 AM, Kostiantyn Ponomarenko wrote: > Hi folks, > > Is there a way to set a node attribute to the "status" section for few > nodes at the same time? > > In my case there is a node attribute which allows some resources to > start in the cluster if it is set. > If I set this node

Re: [ClusterLabs] Query about resource stickiness

On 11/17/2016 06:41 PM, phanidhar prattipati wrote: > Good Morning All, > > I have configured HA on 3 nodes and in order to disable automatic fail > over i need to set resource stickiness value and not sure how to > calculate it. Currently i set it o INFINITY which i believe is not the > right

Re: [ClusterLabs] Locate resource with functioning member of clone set?

On 11/17/2016 11:37 AM, Israel Brewster wrote: > I have a resource that is set up as a clone set across my cluster, > partly for pseudo-load balancing (If someone wants to perform an action > that will take a lot of resources, I can have them do it on a different > node than the primary one), but

Re: [ClusterLabs] Bug in ocf-shellfuncs, ocf_local_nodename function?

On 11/17/2016 11:59 AM, Israel Brewster wrote: > This refers specifically to build version > 5434e9646462d2c3c8f7aad2609d0ef1875839c7 of the ocf-shellfuncs file, on > CentOS 6.8, so it might not be an issue on later builds (if any) or > different operating systems, but it would appear that the >

Re: [ClusterLabs] Pacemaker

On 11/01/2016 02:31 AM, Siwakoti, Ganesh wrote: > Hi, > > > i'm using CentOS release 6.8 (Final) as a KVM and i configured 3 > nodes(PM1.local,PM2.local and PM3.local), and using > CMAN clustering. Resources running at two nodes as Active node then > another one node is for Fail-over resource as

Re: [ClusterLabs] Live migration not working on shutdown

On 10/26/2016 06:12 AM, Rainer Nerb wrote: > Hello all, > > we're currently testing a 2-node-cluster with 2 vms and live migration > on CentOS 7.2 and Pacemaker 1.1.13-10 with disks on iSCSI-targets and > migration via ssh-method. > > Live migration works, if we issue "pcs resource move ...",

Re: [ClusterLabs] Which Pacemaker version is Best.

On 11/01/2016 03:17 AM, Ganesh Siwakoti wrote: > Hello, > > I'm using CentOS release 6.8 (Final) (KVM) and I want to make failover > cluster.i've 2 same nodes for clustering(both are KVM), so which version > of Pacemaker and Cman is appropriate for me? Personally, I'd stick with the packages

Re: [ClusterLabs] packmaker: After migrate a resource, changing resource non-unique param lead to resoruce restart

On 11/03/2016 02:01 AM, 李清硕 wrote: > Hi everyone, > I'm testing pacemaker resoruce live migration, in a simple test > environment with two virtual machines. > The resource is something encapsulated kvm, when i perfrom migrate, for > example, form node1 to node2, > i notice, the pacemaker invoke

[ClusterLabs] Fix in Pacemaker 1.1.15 retroactively assigned CVE-2016-7797

. The vulnerability only affects clusters with Pacemaker Remote nodes. For details, see: http://bugs.clusterlabs.org/show_bug.cgi?id=5269 -- Ken Gaillot <kgail...@redhat.com> ___ Users mailing list: Users@clusterlabs.org http://clusterla

Re: [ClusterLabs] [SECURITY] CVE-2016-7035 - pacemaker - improper IPC guarding

On 11/03/2016 06:03 AM, Jan Pokorný wrote: > Following issue is being publicly disclosed today; more information > regarding the release process will arrive later today and also this > is an opportunity to announce http://clusterlabs.org/wiki/Security > page that was intoduced to help keeping

Re: [ClusterLabs] Coming in 1.1.16: versioned resource parameters

a planned reimplementation that adds functionality and handles rolling upgrades better. It will still be available in the master branch, but not the 1.1 branch. -- Ken Gaillot <kgail...@redhat.com> ___ Users mailing list: Users@clusterlabs.org http://clusterl

Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes

On 10/29/2016 07:55 AM, Ferenc Wágner wrote: > Ken Gaillot <kgail...@redhat.com> writes: > >> This spurred me to complete a long-planned overhaul of Pacemaker >> Explained's "Upgrading" appendix: >> >> http://clusterlabs.org/doc/en-US/Pacemaker/1.

Re: [ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes

On 10/31/2016 11:17 AM, Andrei Borzenkov wrote: > 31.10.2016 17:15, Ken Gaillot пишет: >> On 10/29/2016 07:55 AM, Ferenc Wágner wrote: >>> Ken Gaillot <kgail...@redhat.com> writes: >>> >>>> This spurred me to complete a long-planned overhaul of Pa

[ClusterLabs] Special care needed when upgrading Pacemaker Remote nodes

overhaul of Pacemaker Explained's "Upgrading" appendix: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_upgrading.html Feedback is welcome. -- Ken Gaillot <kgail...@redhat.com> ___ Users mailing list: Users

Re: [ClusterLabs] Antw: Re: Antw: Re: OCFS2 on cLVM with node waiting for fencing timeout

On 10/13/2016 03:36 AM, Ulrich Windl wrote: > That's what I'm talking about: If 1 of 3 nodes is rebooting (or the cluster > is split-brain 1:2), the single node CANNOT continue due to lack of quorum, > while the remaining two nodes can. Is it still necessary to wait for > completion of stonith?

Re: [ClusterLabs] Replicated PGSQL woes

On 10/13/2016 12:04 PM, Israel Brewster wrote: > Summary: Two-node cluster setup with latest pgsql resource agent. > Postgresql starts initially, but failover never happens. > > Details: > > I'm trying to get a cluster set up with Postgresql 9.6 in a streaming > replication using named slots

Re: [ClusterLabs] Colocation and ordering with live migration

On 10/10/2016 07:36 AM, Pavel Levshin wrote: > 10.10.2016 15:11, Klaus Wenninger: >> On 10/10/2016 02:00 PM, Pavel Levshin wrote: >>> 10.10.2016 14:32, Klaus Wenninger: Why are the order-constraints between libvirt & vms optional? >>> If they were mandatory, then all the virtual machines

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

On 10/14/2016 06:56 AM, Nikhil Utane wrote: > Hi, > > Thank you for the responses so far. > I added reverse colocation as well. However seeing some other issue in > resource movement that I am analyzing. > > Thinking further on this, why doesn't "/a not with b" does not imply "b > not with a"?/

Re: [ClusterLabs] Antw: Trying this question again re: arp_interval

On 10/14/2016 03:36 AM, Ulrich Windl wrote: Eric Robinson schrieb am 14.10.2016 um 09:15 in > Nachricht > > >> Does anyone know how many arp_intervals must pass without a reply before

Re: [ClusterLabs] Error performing operation: Argument list too long

On 12/05/2016 02:29 PM, Shane Lawrence wrote: > I'm experiencing a strange issue with pacemaker. It is unable to check > the status of a systemd resource. > > systemctl shows that the service crashed: > [root@xx ~]# systemctl status rsyslog > ● rsyslog.service - System Logging Service >

Re: [ClusterLabs] Antwort: Re: hawk - pacemaker remote

On 12/12/2016 07:05 AM, philipp.achmuel...@arz.at wrote: > >> Von: Ken Gaillot <kgail...@redhat.com> >> An: users@clusterlabs.org >> Datum: 02.12.2016 19:32 >> Betreff: Re: [ClusterLabs] hawk - pacemaker remote >> >> On 12/02/2016 07:38

Re: [ClusterLabs] [cluster-lab] reboot standby node

On 12/11/2016 04:19 PM, Omar Jaber wrote: > Hi all , > > I have cluster contains three nodes with different sore for location > constrain and I have group resource (it’s a service exsists in > /etc/init.d/ folder) > > Running on the node the have the highest score for location >

Re: [ClusterLabs] Random failure with clone of IPaddr2

On 12/15/2016 12:37 PM, al...@amisw.com wrote: > Hi, > > I got some trouble since one week and can't find solution by myself. Any > help will be really appreciated ! > I use corosync / pacemaker for 3 or 4 years and all works well, for > failover or load-balancing. > > I have shared ip between 3

Re: [ClusterLabs] question about dc-deadtime

On 12/15/2016 02:00 PM, Chris Walker wrote: > Hello, > > I have a quick question about dc-deadtime. I believe that Digimer and > others on this list might have already addressed this, but I want to > make sure I'm not missing something. > > If my understanding is correct, dc-deadtime sets the

Re: [ClusterLabs] Random failure with clone of IPaddr2

On 12/15/2016 02:02 PM, al...@amisw.com wrote: >> >> Seeing your configuration might help. Did you set globally-unique=true >> and clone-node-max=3 on the clone? If not, the other nodes can't pick up >> the lost node's share of requests. > > Yes for both, I have globally-unique=true, and I change

Re: [ClusterLabs] Antwort: Re: Antwort: Re: hawk - pacemaker remote

On 12/13/2016 05:26 AM, philipp.achmuel...@arz.at wrote: > >> Von: Kristoffer Grönlund >> An: philipp.achmuel...@arz.at, kgail...@redhat.com, Cluster Labs - >> All topics related to open-source clustering welcomed > >> Datum: 12.12.2016 16:13 >>

Re: [ClusterLabs] Warning: handle_startup_fencing: Blind faith: not fencing unseen nodes

On 12/14/2016 11:14 AM, Denis Gribkov wrote: > Hi Everyone, > > Our company have 15-nodes asynchronous cluster without actually > configured FENCING/STONITH (as I think) features. > > The DC node log getting tons of messages like in subject: > > pengine: warning: handle_startup_fencing: Blind

Re: [ClusterLabs] changing default cib.xml directory

On 12/13/2016 09:57 AM, Christopher Harvey wrote: > I was wondering if it is possible to tell pacemaker to store the cib.xml > file in a specific directory. I looked at the code and searched the web > a bit and haven't found anything. I just wanted to double check here in > case I missed anything.

Re: [ClusterLabs] Antwort: Re: Antwort: Re: clone resource - pacemaker remote

On 12/07/2016 06:26 AM, philipp.achmuel...@arz.at wrote: >> Von: Ken Gaillot <kgail...@redhat.com> >> An: philipp.achmuel...@arz.at, Cluster Labs - All topics related to >> open-source clustering welcomed <users@clusterlabs.org> >> Datum: 05.12.2016 17:38 >&

Re: [ClusterLabs] Nodes see each other as OFFLINE - fence agent (fence_pcmk) may not be working properly on RHEL 6.5

On 12/16/2016 07:46 AM, avinash shankar wrote: > > Hello team, > > I am a newbie in pacemaker and corosync cluster. > I am facing trouble with fence_agent on RHEL 6.5 > I have installed pcs, pacemaker, corosync, cman on RHEL 6.5 on two > virtual nodes (libvirt) cluster. > SELINUX and firewall is

Re: [ClusterLabs] New ClusterLabs logo unveiled :-)

if there's an "official" name, but I've been calling it the "ClusterLabs stack". > On Mon, Jan 2, 2017 at 11:35 AM, Kristoffer Grönlund <kgronl...@suse.com > <mailto:kgronl...@suse.com>> wrote: > > Ken Gaillot <kgail...@redhat.com <mailto:kgail...@re

Re: [ClusterLabs] question about dc-deadtime

rn-series-max=1500 \ > > pe-input-series-max=1500 \ > > pe-error-series-max=1500 \ > > stonith-action=poweroff \ > > stonith-timeout=900 \ > > dc-deadtime=2min \ > > maintenance-mode=false \ > &g

Re: [ClusterLabs] No match for shutdown action on

On 01/10/2017 11:38 AM, Denis Gribkov wrote: > Hi Everyone, > > When I run: > > # pcs resource cleanup resource_name > > I'm getting a block of messages in log on current DC node: > > Jan 10 18:12:13 node1 crmd[21635]: warning: No match for shutdown > action on node2 > Jan 10 18:12:13 node1

Re: [ClusterLabs] simple setup and resources on different nodes??

On 01/11/2017 10:10 AM, lejeczek wrote: > hi eveyone, > I have a simple, test setup, like this: > > $ pcs status > Cluster name: test_cluster > WARNING: corosync and pacemaker node names do not match (IPs used in > setup?) > Stack: corosync > Current DC: work2.whale.private (version

Re: [ClusterLabs] Deleting a variable

On 12/01/2016 01:15 AM, Ulrich Windl wrote: >>>> Ken Gaillot <kgail...@redhat.com> schrieb am 30.11.2016 um 21:39 in >>>> Nachricht > <62cb811f-4396-ff36-ec03-67000b4ed...@redhat.com>: > > [...] >> Once set, attributes are not truly deleted -

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

beforehand with attrd_updater --update-delay or change the delay and value together with --update-both. > 4. Does a delay set only one time work until it's unset (set to 0)? Yes > Thank you, > Kostia > > On Wed, Nov 30, 2016 at 10:39 PM, Ken Gaillot <kgail...@redhat.co

Re: [ClusterLabs] Pacemaker 1.1.16 released

On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: > On Wed, 30 Nov 2016 14:05:19 -0600 > Ken Gaillot <kgail...@redhat.com> wrote: > >> ClusterLabs is proud to announce the latest release of the Pacemaker >> cluster resource manager, version 1.1.15. > >

Re: [ClusterLabs] Antw: Re: Set a node attribute for multiple nodes with one command

be > delayed by that "--delay" which was used when the attribute was set. > > > Thank you, > Kostia > > On Tue, Nov 29, 2016 at 1:08 AM, Ken Gaillot <kgail...@redhat.com > <mailto:kgail...@redhat.com>> wrote: > > On 11/24/2016 05:24 AM, Kos

[ClusterLabs] Pacemaker 1.1.16 released

to all contributors of source code to this release, including Andrew Beekhof, Bin Liu, Christian Schneider, Christoph Berg, David Shane Holden, Ferenc Wágner, Yan Gao, Hideo Yamauchi, Jan Pokorný, Ken Gaillot, Klaus Wenninger, Kostiantyn Ponomarenko, Kristoffer Grönlund, Lars Ellenberg, Masatake Ya

Re: [ClusterLabs] need some help with failing resources

On 12/05/2016 09:30 AM, Darko Gavrilovic wrote: > On 12/5/2016 10:17 AM, Ken Gaillot wrote: >> On 12/03/2016 05:19 AM, Darko Gavrilovic wrote: >>> Here is the output for that resource.. edited >>> >>> primitive svc-mysql ocf:heartbeat:mysql \ >>>

Re: [ClusterLabs] Antwort: Re: clone resource - pacemaker remote

On 12/05/2016 09:20 AM, philipp.achmuel...@arz.at wrote: > Ken Gaillot <kgail...@redhat.com> schrieb am 02.12.2016 19:27:09: > >> Von: Ken Gaillot <kgail...@redhat.com> >> An: users@clusterlabs.org >> Datum: 02.12.2016 19:32 >> Betreff: Re: [Clus

Re: [ClusterLabs] clone resource - pacemaker remote

On 12/02/2016 07:08 AM, philipp.achmuel...@arz.at wrote: > hi, > > what is best way to prevent clone resource trying to run on remote/guest > nodes? location constraints with a negative score:

Re: [ClusterLabs] hawk - pacemaker remote

On 12/02/2016 07:38 AM, philipp.achmuel...@arz.at wrote: > Hi, > > pacemaker remote nodes do not show up in hawk gui. > regarding documentation, this should work - any hints to activate this? > > thank you! > > env: (SLES12.2) > pacemaker-1.1.15-19.15.x86_64 >

Re: [ClusterLabs] Pacemaker 1.1.16 released

On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote: > > > Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot <kgail...@redhat.com> a > écrit : >> On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: >>> On Wed, 30 Nov 2016 14:05:19 -0600 >>&g

<    1   2   3   4   5   6   7   8   9   10   >