Re: [ClusterLabs] Question about fence_mpath

Hi, On Fri, Apr 28, 2017 at 8:09 PM, Chris Adams wrote: > 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

Re: [ClusterLabs] Question about fence_mpath

Once upon a time, Ken Gaillot said: > 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= Hmm, I guess I still don't understand how to use fence_mpath to handle fencing. Do I set

Re: [ClusterLabs] Question about fence_mpath

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

Re: [ClusterLabs] Question about fence_mpath

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

Re: [ClusterLabs] Question about fence_mpath

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

Re: [ClusterLabs] Question about fence_mpath

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.

Re: [ClusterLabs] Question about fence_mpath

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

Re: [ClusterLabs] Question about fence_mpath

Once upon a time, Seth Reid said: > This is part of my multipath.conf that shows the key. > $ cat /etc/multipath.conf > defaults { > user_friendly_names yes > find_multipaths yes > reservation_key 33c5 > } Ah, I should have checked the multipath.conf man page (was just

Re: [ClusterLabs] Question about fence_mpath

> > The man page talks about it > unique to each node (but you only create the STONITH object from one > node, right?). The key is unique to each node, but there is only on stonith object. For fence_mpath, they are putting scsi keys on a shared stonith device. It also says it has to be set in

[ClusterLabs] Question about fence_mpath

I am trying to set up a new cluster using fence_mpath. I'm not sure what to use for the "key" value though. The man page talks about it unique to each node (but you only create the STONITH object from one node, right?). It also says it has to be set in /etc/multipath.conf but then doesn't say