haproxy – The pacemaker fencing is not triggered

I have 2 nodes:
– patroni1: 192.168.1.38
– patroni2: 192.168.1.39

and virtual IP address: 192.168.1.40

I have HA-Proxy installed on both.

Here is the status of my computers when VIP is associated with patroni2 and haproxy is enabled on patroni2.

-----------
[root@patroni1 ~]Number of pieces
Cluster name: haproxy_cluster
Battery: corosync
Current CD: patroni2 (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Thu 29 Nov 21:29:00 2018
Last change: Thu 29 Nov 21:24:52 2018 by root via cibadmin on patroni1

2 configured nodes
4 configured resources

Online: [ patroni1 patroni2 ]

Complete list of resources:

xen-fencing-patroni2 (stonith: fence_xenapi): started patroni1
xen-fencing-patroni1 (stonith: fence_xenapi): started patroni2
Resource Group: HAproxyGroup
haproxy (ocf :: heartbeat: haproxy): Starting patroni2
VIP (ocf :: heartbeat: IPaddr2): Starting clienti2

Status of the demon:
corosync: active / enabled
Pacemaker: active / activated
pcsd: active / enabled
[root@patroni1 ~]# pcs resource show VIP
Resource: VIP (class = provider ocf = heartbeat type = IPaddr2)
Attributes: cidr_netmask = 24 ip = 192.168.1.40
Operations: monitoring interval = 1s (VIP-monitor-interval-1s)
start interval = 0s delay time = 20s (VIP-start-interval-0s)
shutdown interval = 0s delay time = 20s (VIP-stop-interval-0s)
[root@patroni1 ~]# resources pcs show haproxy
Resource: haproxy (class = provider ocf = heartbeat type = haproxy)
Attributes: binpath = / usr / sbin / haproxy conffile = / etc / haproxy / haproxy.cfg
Operations: monitoring interval = 10s (haproxy-monitor-interval-10s)
startup interval = 0s delay time = 20s (haproxy-start-interval-0s)
stop interval = 0s timeout = 20s (haproxy-stop-interval-0s)

-----------

My problem is this: Fencing is not triggered whenever I manually kill haproxy on patroni2. Fencing is only triggered when I manually stop or restart patroni2.

here is the status of pcs when i manually kill haproxy

------------
[root@patroni1 ~]Number of pieces
Cluster name: haproxy_cluster
Battery: corosync
Current CD: patroni2 (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
Last updated: Thu 29 Nov 21:37:37 2018
Last change: Thu 29 Nov 21:24:52 2018 by root via cibadmin on patroni1

2 configured nodes
4 configured resources

Online: [ patroni1 patroni2 ]

Complete list of resources:

xen-fencing-patroni2 (stonith: fence_xenapi): started patroni1
xen-fencing-patroni1 (stonith: fence_xenapi): started patroni2
Resource Group: HAproxyGroup
haproxy (ocf :: heartbeat: haproxy): Starting patroni2
VIP (ocf :: heartbeat: IPaddr2): start of patroni2

Failed actions:
* haproxy_monitor_10000 on patroni2 not running (7): call = 38, status = complete, exitreason = & # 39; & # 39 ;,
last-rc-change = "Thu 29 Nov 21:37:36 2018", in queue = 0ms, exec = 0ms


Status of the demon:
corosync: active / enabled
Pacemaker: active / activated
pcsd: active / enabled

------------

How to make fencing be handled when HA-Proxy does not respond?

cordially
-bino-