keepalived 日志信息:

Dec 13 01:13:33 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:36 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:39 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:42 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:45 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:48 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:51 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:54 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:13:57 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:14:00 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:14:03 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:14:06 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1
Dec 13 01:14:09 node200 Keepalived_vrrp[3692]: /etc/keepalived/check-apiserver.sh exited with status 1

但是其实api-server是启动的

命令行直接运行脚本是没有问题的

[root@node200 ~]# /etc/keepalived/check-apiserver.sh
success!
[root@node200 ~]#

api-server 是正常的

[root@node200 ~]# /etc/keepalived/check-apiserver.sh
success!
[root@node200 ~]# systemctl status kube-apiserver.service
● kube-apiserver.service - Kubernetes API Server
   Loaded: loaded (/etc/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2020-12-13 00:06:52 PST; 1h 10min ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
 Main PID: 4060 (kube-apiserver)
   CGroup: /system.slice/kube-apiserver.service
           └─4060 /opt/kubernetes/bin/kube-apiserver --enable-admission-plugins=NamespaceLifecycle,NodeRestrictio...

Dec 13 01:16:35 node200 kube-apiserver[4060]: I1213 01:16:35.087340    4060 clientconn.go:948] ClientConn swi...rst"
Dec 13 01:16:35 node200 kube-apiserver[4060]: I1213 01:16:35.087496    4060 balancer_conn_wrappers.go:78] pic...il>}
Dec 13 01:16:35 node200 kube-apiserver[4060]: I1213 01:16:35.094516    4060 balancer_conn_wrappers.go:78] pic...il>}
Dec 13 01:16:35 node200 kube-apiserver[4060]: I1213 01:16:35.095357    4060 controlbuf.go:508] transport: loo...ing"
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.807648    4060 client.go:360] parsed scheme: "pa...ugh"
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.807729    4060 passthrough.go:48] ccResolverWrap...il>}
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.807740    4060 clientconn.go:948] ClientConn swi...rst"
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.808137    4060 balancer_conn_wrappers.go:78] pic...il>}
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.815762    4060 balancer_conn_wrappers.go:78] pic...il>}
Dec 13 01:16:44 node200 kube-apiserver[4060]: I1213 01:16:44.816693    4060 controlbuf.go:508] transport: loo...ing"
Hint: Some lines were ellipsized, use -l to show in full.
[root@node200 ~]#

有没有办法调试这个脚本, 或者有没有人知道这个是咋回事