haproxy log 提示Connection refused

[yexingqi]

请问一下ansible推送K8S成功后，发现haproxy一直报错，以下的二台node节点提示layer4错误。请问我该如保排查修复呢？ 谢谢！

systemctl status haproxy
● haproxy.service - HAProxy Load Balancer
Loaded: loaded (/lib/systemd/system/haproxy.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-09-28 09:12:10 UTC; 16s ago
Docs: man:haproxy(1)
file:/usr/share/doc/haproxy/configuration.txt.gz
Process: 3052 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS)
Main PID: 3054 (haproxy)
Tasks: 5 (limit: 4620)
Memory: 8.8M
CGroup: /system.slice/haproxy.service
├─3054 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock
└─3065 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock

Sep 28 09:12:10 k8s-sh-03 systemd[1]: Stopped HAProxy Load Balancer.
Sep 28 09:12:10 k8s-sh-03 systemd[1]: Starting HAProxy Load Balancer...
Sep 28 09:12:10 k8s-sh-03 haproxy[3054]: [NOTICE] 271/091210 (3054) : New worker #1 (3065) forked
Sep 28 09:12:10 k8s-sh-03 systemd[1]: Started HAProxy Load Balancer.
Sep 28 09:12:12 k8s-sh-03 haproxy[3065]: [WARNING] 271/091212 (3065) : Server ingress-node/10.10.10.168 is DOWN, reason: Layer4 connection problem, info: "Connection >
Sep 28 09:12:13 k8s-sh-03 haproxy[3065]: [WARNING] 271/091213 (3065) : Server ingress-node/10.10.10.167 is DOWN, reason: Layer4 connection problem, info: "Connection >
Sep 28 09:12:13 k8s-sh-03 haproxy[3065]: [ALERT] 271/091213 (3065) : proxy 'ingress-node' has no server available!
Sep 28 09:12:14 k8s-sh-03 haproxy[3065]: [WARNING] 271/091214 (3065) : Server ingress-node-tls/10.10.10.168 is DOWN, reason: Layer4 connection problem, info: "Connect>
Sep 28 09:12:14 k8s-sh-03 haproxy[3065]: [WARNING] 271/091214 (3065) : Server ingress-node-tls/10.10.10.167 is DOWN, reason: Layer4 connection problem, info: "Connect>
Sep 28 09:12:14 k8s-sh-03 haproxy[3065]: [ALERT] 271/091214 (3065) : proxy 'ingress-node-tls' has no server available!

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.