- I've set
stonith-timeoutas an attribute on my
stonithdevice, but I'm still seeing timeouts that are shorter than the value I set
stonith-timeoutdoesn't seem to work on a per-device basis like the manpages and docs say it should
- Why doesn't
stonith-timeoutapply correctly to my cluster's stonith devices? I have to set the cluster property
stonith-timeoutfor all of them.
- I've set the
stonith-timeoutproperty to a higher value, but
monitoractions are timing out
statusactions? Or just to fencing a node (i.e., reboot).
- My cluster logs errors from my
stonithdevice regarding a parse error from
Aug 31 08:23:39 node1 stonith-ng: warning: log_operation: vmfence1:6167 [ Parse error: Ignoring unknown option 'stonith-timeout=120' ]
- Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
- One or more
stonith-timeoutset as an attribute
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.