SBD Fencing required / without Block Storage

Hi there

I have a Problem with the SBD-Fencing.

I set up the Cluster without the SBD-Fencing but it seems that I can’t add an Apache Server without the SBD-Fencing. I got this error Message, when I used the wizard to add the Apache:

Failed to apply configuration (rc=1)
warning: unpack_config: Blind faith: not fencing unseen nodes

If I understand it right, I have to use SBD-Fencing to add the Apache.
That leads me to my next Problem. In our company we can only use File Storage (in my cas a NAS) which doesn’t seem to work with SBD-Fencing.

Is there a way to circumvent the SBD-Fencing od at least do it with my File Storage device?

[QUOTE=natachawalther;58894]Hi there

I have a Problem with the SBD-Fencing.

I set up the Cluster without the SBD-Fencing but it seems that I can’t add an Apache Server without the SBD-Fencing. I got this error Message, when I used the wizard to add the Apache:

Failed to apply configuration (rc=1)
warning: unpack_config: Blind faith: not fencing unseen nodes

If I understand it right, I have to use SBD-Fencing to add the Apache.
That leads me to my next Problem. In our company we can only use File Storage (in my cas a NAS) which doesn’t seem to work with SBD-Fencing.

Is there a way to circumvent the SBD-Fencing od at least do it with my File Storage device?[/QUOTE]

Actually pacemaker supports lots of fencing mechanism and you need to pick at least 1 (but you coiuld have multiple fencing ‘devices’).
For the list of currently available (installed) fencing resources, run:

crm ra list stonith

To get info for a specific fencing resource:

crm ra info 'stonith:fence_rhevm' 

Once you create your stonith resoource(s) , you need to update a property which the custer uses to know if any fencing mechanism is available:

crm configure property stonith-enabled=true

As fencing should be executed prior the switch of your resources , you either need to setup fencing and enable it (see previous post) or disable fencing (previous command but with ‘false’) and have no support for your cluster.
You need to properly test fencing prior putting the cluster in production:

 crm node fence <nodename>

Even pacemaker mailing list will not help you without fencing.