On October 1, 2018 8:01:36 PM UTC, Patrick Whitney
wrote:
[...]
>so we were lucky enough our test environment is a KVM/libvirt
>environment,
>so I used fence_virsh. Again, I had the same problem... when the "bad"
>node was fenced, dlm_controld would issue (what appears to be) a
>fence_all,
Hi Ulrich,
When I first encountered this issue, I posted this:
https://lists.clusterlabs.org/pipermail/users/2018-September/015637.html
... I was using resource fencing in this example, but, as I've mentioned
before, the issue would come about, not when fencing occurred, but when the
fenced
Hi!
It would be much more helpful, if you could provide logs around the problem
events. Personally I think you _must_ implement proper fencing. In addition,
DLM seems to do its own fencing when there is a communication problem.
Regards,
Ulrich
>>> Patrick Whitney 01.10.18 16.25 Uhr >>>
Hi
