Re: [ClusterLabs] fence_scsi no such device

2016-03-21 Thread Jan Pokorný
On 21/03/16 09:46 -0500, Ken Gaillot wrote: > You need more attributes, such as "devices" to specify which SCSI > devices to cut off, and either "key" or "nodename" to specify the > node key for SCSI reservations. Hmm, I keep lamenting that by extending agents metadata with inline RelaxNG grammar

[ClusterLabs] Error creating a fence mechanism

2016-03-21 Thread Douglas Restrepo
Hi guys, Im trying to create a new cluster using pacemaker but Im having a problem with the fence mechanism.Until de moment I have perform the following tasks: + I have installed two different machines with centos 7 (infrastructure mode).+ Each machine have been configured with two network

Re: [ClusterLabs] no clone for pcs-based cluster fencing?

2016-03-21 Thread Devin Reade
--On Monday, March 21, 2016 09:22:40 AM -0500 Ken Gaillot wrote: It's actually newer pacemaker versions rather than pcs itself. Fence agents do not need to be cloned, or even running -- as long as they're configured and enabled, any node can use the resource. Excellent.

Re: [ClusterLabs] Antw: Re: no clone for pcs-based cluster fencing?

2016-03-21 Thread Ken Gaillot
On 03/21/2016 09:34 AM, Ulrich Windl wrote: Ken Gaillot schrieb am 21.03.2016 um 15:22 in Nachricht > <56f003b0.4020...@redhat.com>: > > [...] >> It's actually newer pacemaker versions rather than pcs itself. Fence >> agents do not need to be cloned, or even

Re: [ClusterLabs] fence_scsi no such device

2016-03-21 Thread Ken Gaillot
On 03/21/2016 08:39 AM, marvin wrote: > > > On 03/15/2016 03:39 PM, Ken Gaillot wrote: >> On 03/15/2016 09:10 AM, marvin wrote: >>> Hi, >>> >>> I'm trying to get fence_scsi working, but i get "no such device" error. >>> It's a two node cluster with nodes called "node01" and "node03". The OS >>>

[ClusterLabs] Antw: Re: no clone for pcs-based cluster fencing?

2016-03-21 Thread Ulrich Windl
>>> Ken Gaillot schrieb am 21.03.2016 um 15:22 in >>> Nachricht <56f003b0.4020...@redhat.com>: [...] > It's actually newer pacemaker versions rather than pcs itself. Fence > agents do not need to be cloned, or even running -- as long as they're > configured and enabled, any

Re: [ClusterLabs] no clone for pcs-based cluster fencing?

2016-03-21 Thread Ken Gaillot
On 03/20/2016 06:20 PM, Devin Reade wrote: > I'm looking at a new pcs-style two node cluster running on CentOS 7 > (pacemaker 1.1.13, corosync 2.3.4) and crm_mon shows this line > for my fencing resource, that is the resource running on only one of > the two nodes: > >fence_cl2

Re: [ClusterLabs] fence_scsi no such device

2016-03-21 Thread marvin
On 03/15/2016 03:39 PM, Ken Gaillot wrote: On 03/15/2016 09:10 AM, marvin wrote: Hi, I'm trying to get fence_scsi working, but i get "no such device" error. It's a two node cluster with nodes called "node01" and "node03". The OS is RHEL 7.2. here is some relevant info: # pcs status Cluster

Re: [ClusterLabs] Antw: Re: Antw: Re: Cluster failover failure with Unresolved dependency

2016-03-21 Thread Lorand Kelemen
Of course, to catch you up: >> Still experiencing the same behaviour, killing amavisd returns an rc=7 for >> the monitoring operation on the "victim" node, this soungs logical, but the >> logs contain the same: amavisd and virtualip cannot run anywhere. >> >> I made sure systemd is clean (amavisd

[ClusterLabs] Antw: Re: PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)

2016-03-21 Thread Ulrich Windl
>>> Dennis Jacobfeuerborn schrieb am 19.03.2016 um >>> 14:32 in Nachricht <56ed5507.7070...@conversis.de>: > On 17.03.2016 08:45, Andrei Borzenkov wrote: >> On Wed, Mar 16, 2016 at 9:35 PM, Mike Bernhardt wrote: >>> I guess I have to say "never mind!"

Re: [ClusterLabs] Antw: Re: Cluster failover failure with Unresolved dependency

2016-03-21 Thread Lorand Kelemen
Reproduced it again: Last updated: Mon Mar 21 10:01:18 2016 Last change: Mon Mar 21 09:59:27 2016 by root via crm_attribute on mail1 Stack: corosync Current DC: mail2 (version 1.1.13-10.el7_2.2-44eb2dd) - partition with quorum 2 nodes and 10 resources configured Online: [ mail1 mail2 ]

[ClusterLabs] Antw: Re: Cluster failover failure with Unresolved dependency

2016-03-21 Thread Ulrich Windl
>>> Lorand Kelemen schrieb am 18.03.2016 um 16:42 in Nachricht : > I reviewed all the logs, but found nothing out of the ordinary, besides the > "resource cannot run anywhere" line, however after the