[ClusterLabs] Problem with a ping resource on CentOS 8

Andrei Borzenkov arvidjaar at gmail.com
Fri Aug 27 12:05:26 EDT 2021


On Fri, Aug 27, 2021 at 6:33 PM <fatcharly at gmx.de> wrote:
>
> Hi,
>
> I'm running a two node cluster on CentOS Linux release 8.4.2105 4.18.0-305.12.1.el8_4.x86_64 with the following pacemaker:
> pacemaker-2.0.5-9.el8_4.1.x86_64
> pacemaker-cluster-libs-2.0.5-9.el8_4.1.x86_64
> pacemaker-libs-2.0.5-9.el8_4.1.x86_64
> pacemaker-schemas-2.0.5-9.el8_4.1.noarch
> pacemaker-cli-2.0.5-9.el8_4.1.x86_64
>
> Both Nodes communicate with each other and the defined HA-IP's are working fine.
> But when I add a ping-resource:
>
> pcs resource create ping_fw ocf:pacemaker:ping dampen=5s multiplier=1000 host_list=192.168.20.1 clone
>
> and a constraint location:
>
> pcs constraint location HA-IP_211 rule score=-INFINITY ping_fw lt 1 or not_defined ping_fw
>
> the cluster stops the HA-IP resources.
>

Default attribute name is "pingd", not resource name.


More information about the Users mailing list