Re: [ClusterLabs] Question about fence_mpath

[Ken Gaillot]

On 04/28/2017 03:37 PM, Chris Adams wrote:
> Once upon a time, Seth Reid  said:
>> This confused me too when I set up my cluster. I found that everything
>> worked better if I didn't specify a device path. I think there was
>> documentation on Redhat that led me to try removing the "device" options.
> 
> fence_mpath won't work without device(s).  However, I figured out my
> problem: I needed to set pmck_host_check=none (both nodes in my cluster
> can handle fencing).  Then everything seems to work.

You only want pcmk_host_check=none if the fence device can fence either
node. If the device can only fence one node, you want
pcmk_host_list=


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Question about fence_mpath

[Chris Adams]

Once upon a time, Seth Reid  said:
> This confused me too when I set up my cluster. I found that everything
> worked better if I didn't specify a device path. I think there was
> documentation on Redhat that led me to try removing the "device" options.

fence_mpath won't work without device(s).  However, I figured out my
problem: I needed to set pmck_host_check=none (both nodes in my cluster
can handle fencing).  Then everything seems to work.

-- 
Chris Adams 

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Question about fence_mpath

[Seth Reid]

On Fri, Apr 28, 2017 at 11:25 AM, Chris Adams  wrote:

> Once upon a time, Seth Reid  said:
> > I've had a similar problem. Make sure that the /dev/mapper object above
> > isn't a symlink. In my multiparth.conf, I had added an alias to a device
> > name, like that, to make it easier, but if I pointed my fencing at that,
> it
> > didn't work. However, I could point directly to the object that the
> symlink
> > pointed to, and it work. I actually had better luck not even specifying a
> > device at all. It found the right one.
>
> But the multipath devices are always symlinks - how do you access it?
> The only "real" devices are /dev/dm-, but those names are not
> stable, so you can't use those for anything.


This confused me too when I set up my cluster. I found that everything
worked better if I didn't specify a device path. I think there was
documentation on Redhat that led me to try removing the "device" options.

Also thinking back, I'm using fence_scsi, but in a multipath environment.
Fence_scsi detected the shared device and everything worked very very
smoothly for me. I apologize for not realizing that I had used fence_scsi
(and not fence_mpath), but give it a shot removing the "device" options
from your stonith command.


>
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] pacemaker daemon shutdown time with lost remote node

[Radoslaw Garbacz]

Hi,

I have a question regarding pacemaker daemon shutdown
procedure/configuration.

In my case, when a remote node is lost pacemaker needs exactly 10minutes to
shutdown, during which there is nothing logged.
So my questions:
1. What is pacemaker doing at this time?
2. How to make it shorter?


Changed Pacemaker Configuration:
- cluster-delay
- dc-deadtime


Pacemaker Logs:
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
crm_signal_dispatch: Caught 'Terminated' signal | 15 (invoking handler)
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
pcmk_shutdown_worker:Shutting down Pacemaker
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
stop_child:  Stopping crmd | sent signal 15 to process 17698
Apr 28 17:48:07 [17695] ip-10-41-177-183   lrmd: info:
cancel_recurring_action: Cancelling ocf operation
monitor_head_monitor_191000
Apr 28 17:48:07 [17695] ip-10-41-177-183   lrmd: info:
log_execute: executing - rsc:monitor_head action:stop call_id:130
[...]
Apr 28 17:48:07 [17689] ip-10-41-177-183 pacemakerd: info: main:
Exiting pacemakerd
Apr 28 17:48:07 [17689] ip-10-41-177-183 pacemakerd: info:
crm_xml_cleanup: Cleaning up memory from libxml2


Pacemaker built from github: 1.16


Help greatly appreciated.

-- 
Best Regards,

Radoslaw Garbacz
XtremeData Incorporated
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Question about fence_mpath

[Chris Adams]

Once upon a time, Seth Reid  said:
> I've had a similar problem. Make sure that the /dev/mapper object above
> isn't a symlink. In my multiparth.conf, I had added an alias to a device
> name, like that, to make it easier, but if I pointed my fencing at that, it
> didn't work. However, I could point directly to the object that the symlink
> pointed to, and it work. I actually had better luck not even specifying a
> device at all. It found the right one.

But the multipath devices are always symlinks - how do you access it?
The only "real" devices are /dev/dm-, but those names are not
stable, so you can't use those for anything.

-- 
Chris Adams 

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Question about fence_mpath

[Chris Adams]

So, I'm still not getting fence_mpath working.  This is all on CentOS 7.
Here's what I did:

- on each node, put a unique "reservation_key" in /etc/multipath.conf
  defaults{} section (node1=20170001 and node2=20170002)

- created the STONITH device on node1 with:
  pcs stonith create multipath fence_mpath 
devices=/dev/mapper/36000d31001309643 key=20170001 meta 
provides=unfencing

It creates, but any time anything tries to fence (manually or by
rebooting a node), I get errors in /var/log/messages.  Trying to
manually fence a node gets:

# pcs stonith fence node2 --off
Error: unable to fence 'node2'
Command failed: No such device

Another issue I run into is that fence_mpath tries to access/write to
/var/run/cluster/mpath.devices, but nothing else creates that directory
(and it seems that fence_mpath tries to read from it before writing it
out).

Anybody using fence_mpath as a STONITH device with pacemaker/corosync on
CentOS 7?
-- 
Chris Adams 

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] should such a resource set work?

[Ken Gaillot]

On 04/28/2017 08:17 AM, lejeczek wrote:
> hi everybody
> 
> I have a set:
> 
> set IP2 IP2 IP2 LVM(exclusive) mountpoint smb smartd sequential=true
  ^^^

Is this a typo?

> setoptions score=INFINITY
> 
> it should work, right?
> 
> yet when I standby a node and I see cluster jumps straight to mountpoint
> and fails:
> 
> Failed Actions:
> * aLocalStorage5mnt_start_0 on nodeA 'not installed' (5): call=918,
> status=complete, exitreason='Couldn't find device
> [/dev/mapper/0-raid10.A]. Expected /dev/??? to exist',
> 
> Where am I making a mistake?
> thanks
> L.

Is this in a location, colocation, or order constraint?

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] should such a resource set work?

[lejeczek]

hi everybody

I have a set:

set IP2 IP2 IP2 LVM(exclusive) mountpoint smb smartd 
sequential=true setoptions score=INFINITY


it should work, right?

yet when I standby a node and I see cluster jumps straight 
to mountpoint and fails:


Failed Actions:
* aLocalStorage5mnt_start_0 on nodeA 'not installed' (5): 
call=918, status=complete, exitreason='Couldn't find device 
[/dev/mapper/0-raid10.A]. Expected /dev/??? to exist',


Where am I making a mistake?
thanks
L.

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] resource group vs colocation

[Tomas Jelinek]

Dne 27.4.2017 v 23:13 Ken Gaillot napsal(a):

On 04/27/2017 02:02 PM, lejeczek wrote:

hi everyone

I have a group and I'm trying to colocate - sounds strange - order with
the group is not how I want it.
I was hoping that with colocation set I can reorder the resources - can
I? Because .. something, or my is not getting there.
I have within a group:

IP
mount
smb
IP1

and I colocated sets:

set IP IP1 sequential=false set mount smb

and yet smb would not start on IP1. I see resource are still being order
as they list.

Could somebody shed more light on what is wrong and group vs colocation
subject?

m. thanks
L.


A group is a shorthand for colocation and order constraints between its
members. So, you should use either a group, or a colocation set, but not
both with the same members.

If you simply want to reorder the sequence in which the group members
start, just recreate the group, listing them in the order you want. That


If you're using pcs, you can change the order of resources within an 
existing group with the "pcs resource group add" command and --before or 
--after options. For example

pcs resource group add your_group IP1 --after IP
changes your group like this
IP
IP1
mount
smb


is, the first member of the group will be started first, then the second
member, etc.

If you prefer using sets, then don't group the resources -- use separate
colocation and ordering constraints with the sets, as desired.

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org