[ClusterLabs] fence_sanlock and pacemaker

Andrew Beekhof andrew at beekhof.net
Wed Aug 26 18:12:35 EDT 2015

> On 27 Aug 2015, at 4:11 am, Laurent B. <laurentb at qmail.re> wrote:
> Gents,
> I'm trying to configure a HA cluster with RHEL 6.5. Everything goes well
> except the fencing. The cluster's node are not connected to the
> management lan (where stand all the iLO/UPS/APC devices) and it's not
> planned to connecting them to this lan.
> With these constraints, I figured out that a way to get fencing working
> is to use *fence_sanlock*. I followed this tutorial:
> https://alteeve.ca/w/Watchdog_Recovery and I it worked (I got some
> problem with SELinux that I finally disabled like specified in the
> following RHEL 6.5 release note:
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.5_Technical_Notes/
> )
> So perfect. The problem is that fence_sanlock relies on cman and not
> pacemaker. So with stonith disabled, pacemaker restarts the resources
> without waiting for the victim to be fenced and with stonith enabled,
> pacemaker complains about the lack of stonith resources and block all
> the cluster.
> I tried to put fence_sanlock as a stonith resource at the pacemaker
> level but as explained there
> http://oss.clusterlabs.org/pipermail/pacemaker/2013-May/017980.html it
> does not work and as explained there
> https://bugzilla.redhat.com/show_bug.cgi?id=962088 it's not planned to
> make it work.
> My question: is there a workaround ?

You’d have to build it yourself, but sbd could be an option

> Thank you,
> Laurent
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://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

More information about the Users mailing list