Hi Klaus,
Thank you very much, that is what the problem was, Pacemaker was using
short hostnames, but SBD was using fully qualified hostnames. I am able to
successfully fence the host now that they both agree on hostname values.
Thanks,
Phil Stedman
Db2 High Availability Development and Support
Email: pmste...@us.ibm.com
From: Klaus Wenninger <kwenn...@redhat.com>
To: Cluster Labs - All topics related to open-source clustering
welcomed <users@clusterlabs.org>
Date: 09/22/2020 12:04 AM
Subject: [EXTERNAL] Re: [ClusterLabs] SBD fencing not working on my
two-node cluster
Sent by: "Users" <users-boun...@clusterlabs.org>
On 9/22/20 8:19 AM, Andrei Borzenkov wrote:
> 22.09.2020 02:06, Philippe M Stedman пишет:
>> Hi Strahil,
>>
>> Here is the output of those commands.... I appreciate the help!
>>
>> # crm config show
>> node 1: ceha03 \
>> attributes ethmonitor-ens192=1
>> node 2: ceha04 \
>> attributes ethmonitor-ens192=1
>> (...)
>> primitive stonith_sbd stonith:fence_sbd \
> Try external/sbd agent. So far I have never had any issue with it.
>
>> params devices="/dev/sde1" \
> What is output of
>
> sbd -d /dev/sde1 list
If what you're getting doesn't match the node-names as pacemaker
sees them you can enforce the names used by sbd in the config-file
with the '-n' option. (alternatively setup pcmk_host_map)
>
> on all nodes? Also try to add sbd_path parameter to point to sbd binary
> location - it is possible that fence_sbd does not find it.
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home:
https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
