在k8s集群上部署GlusterFS-就绪探针失败:/usr/local/bin/status-probe.sh [英] GlusterFS deployment on k8s cluster-- Readiness probe failed: /usr/local/bin/status-probe.sh
问题描述
设置:k8s(AKS)集群上的GlusterFS；
Setup: GlusterFS on k8s(AKS) cluster;
使用gk-deploy部署glusterfs时出现问题；下面共享了一些错误摘要，请提出解决方法以使我的部署继续进行-谢谢.
Having issue while glusterfs deploy using gk-deploy; below shared few error snippets please suggest workaround to get my deployment going- thanks in advance.
得到相同的错误:事件:从消息中键入原因年龄---- ------ ---- ---- -------警告不健康的8m44s(x459超过3h45m)kubelet，aks-nodepool1-70391060-0就绪探针失败: /usr/local/bin/status-probe.sh检查失败:systemctl -q是活动的 gluster-blocked.service警告不健康4m2s(x462超过3h46m) kubelet，aks-nodepool1-70391060-0活动探针失败: /usr/local/bin/status-probe.sh检查失败:systemctl -q是活动的 gluster-blocked.service
Getting same error : Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 8m44s (x459 over 3h45m) kubelet, aks-nodepool1-70391060-0 Readiness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active gluster-blockd.service Warning Unhealthy 4m2s (x462 over 3h46m) kubelet, aks-nodepool1-70391060-0 Liveness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active gluster-blockd.service
当我检查处于暗淡状态的吊舱-它看起来成功时，是什么原因导致准备就绪报告失败-有任何想法/想法吗?
When i inspect the pod with the glusterd status - it looks successful, what might be causing the reporting on readiness failed - any ideas / thoughts?
推荐答案
探针不仅检查glusterd.service的状态.还有其他一些要考虑的事项.可以从github 获得 status-probe.sh脚本>.消息
The probe does not only check for the status of the glusterd.service. There are a few other things that are taken into account. The status-probe.sh script is available from github. The message
Liveness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active gluster-blockd.service
表示gluster-blockd.service运行不正常.这可能有不同的原因，您需要检查gluster-blockd.log和tcmu-runner.log来找出问题所在.
indicates that gluster-blockd.service is not running correctly. This can have different causes, you would need to inspect the gluster-blockd.log and tcmu-runner.log to find out what the problem is.
gluster-blockd.service是可选的.如果您的环境中不需要使用type = block的PersistentVolumes，则可以禁用该检查.
gluster-blockd.service is optional. If you do not need PersistentVolumes with type=block in your environment, you can disable the check.
在守护程序的规范中，您可以更改环境变量GLUSTER_BLOCKD_STATUS_PROBE_ENABLE并将其值设置为"0".
In the specification of the daemonset, you can change the environment variable GLUSTER_BLOCKD_STATUS_PROBE_ENABLE and set the value to "0".
这篇关于在k8s集群上部署GlusterFS-就绪探针失败:/usr/local/bin/status-probe.sh的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
