3.0.0 apiserver CrashLoopBackOff

rayzhou2017

hqq_get 我不知道，官网很明确用黑体字说了, Do not use these releases

Cauchy

hqq_get
k8s集群是否进行过升级？集群中有几个master呢？每个master的kube-apiserver版本是否一致？

zhanmin

问题解决了吗？我也遇到了

hqq_get

zhanmin 没有，同样的方法换个新的干净的集群就起来了

MingZhang-YBPS

只要是用kubesphere-delete.sh卸载过，然后重装kubesphere。这个问题基本上是必现的。
K8S版本1.18.0，CNI calico

valiner

救救孩子吧，该怎么解决这个问题

hongming

valiner 奉上秘籍： https://kubernetes.io/zh/docs/tasks/debug-application-cluster/debug-service/

Roytin

我也遇到了这个问题。原本运行正常的，在一次服务器重启之后，kubesphere登不上去了，报500，kubectl get pod一看ks-apiserver CrashLoopBackOff

[root@c1 ~]# kubectl get pod -n kubesphere-system
NAME                                     READY   STATUS             RESTARTS   AGE
ks-apiserver-5c88c4b9c8-45cmw            0/1     CrashLoopBackOff   7          15m
ks-apiserver-5c88c4b9c8-q8gnk            0/1     CrashLoopBackOff   7          16m
ks-apiserver-785d5cc779-w946t            1/1     Running            0          21h
ks-console-65f4d44d88-6gjp6              1/1     Running            1          7d4h
ks-console-65f4d44d88-94llq              1/1     Running            0          76m
ks-console-65f4d44d88-d99g6              1/1     Running            1          7d5h
ks-controller-manager-6b5cbbdcf5-gx95b   1/1     Running            0          69m
ks-controller-manager-6b5cbbdcf5-q7vnj   1/1     Running            0          68m
ks-controller-manager-6b5cbbdcf5-wzcwj   1/1     Running            1          68m
ks-installer-69df988b79-c5dgk            1/1     Running            2          21h
minio-859cb4d777-68mhb                   1/1     Running            2          21h
openldap-0                               1/1     Running            1          7d5h
openldap-1                               1/1     Running            3          9d
openpitrix-import-job-nld9h              0/1     Completed          0          70m
redis-ha-haproxy-868fdbddd4-cpq64        1/1     Running            0          17m
redis-ha-haproxy-868fdbddd4-nntmc        1/1     Running            0          16m
redis-ha-haproxy-868fdbddd4-qdv2v        1/1     Running            0          16m
redis-ha-server-0                        2/2     Running            0          13m
redis-ha-server-1                        2/2     Running            0          13m
redis-ha-server-2                        2/2     Running            0          11m

查看pod logs也是说redis访问失败。

Roytin

我也遇到了这个问题。原本运行正常的，在一次服务器重启之后，kubesphere登不上去了，报500，kubectl get pod一看ks-apiserver CrashLoopBackOff

[root@c1 ~]# kubectl get pod -n kubesphere-system
NAME                                     READY   STATUS             RESTARTS   AGE
ks-apiserver-5c88c4b9c8-45cmw            0/1     CrashLoopBackOff   7          15m
ks-apiserver-5c88c4b9c8-q8gnk            0/1     CrashLoopBackOff   7          16m
ks-apiserver-785d5cc779-w946t            1/1     Running            0          21h
ks-console-65f4d44d88-6gjp6              1/1     Running            1          7d4h
ks-console-65f4d44d88-94llq              1/1     Running            0          76m
ks-console-65f4d44d88-d99g6              1/1     Running            1          7d5h
ks-controller-manager-6b5cbbdcf5-gx95b   1/1     Running            0          69m
ks-controller-manager-6b5cbbdcf5-q7vnj   1/1     Running            0          68m
ks-controller-manager-6b5cbbdcf5-wzcwj   1/1     Running            1          68m
ks-installer-69df988b79-c5dgk            1/1     Running            2          21h
minio-859cb4d777-68mhb                   1/1     Running            2          21h
openldap-0                               1/1     Running            1          7d5h
openldap-1                               1/1     Running            3          9d
openpitrix-import-job-nld9h              0/1     Completed          0          70m
redis-ha-haproxy-868fdbddd4-cpq64        1/1     Running            0          17m
redis-ha-haproxy-868fdbddd4-nntmc        1/1     Running            0          16m
redis-ha-haproxy-868fdbddd4-qdv2v        1/1     Running            0          16m
redis-ha-server-0                        2/2     Running            0          13m
redis-ha-server-1                        2/2     Running            0          13m
redis-ha-server-2                        2/2     Running            0          11m

查看pod logs也是说redis访问失败。

后来换了个机器也是解决了。

再后来，IT告诉我分我的机器是HyperV上的虚拟机，重启是因为那台物理机上内存吃紧就给我改了动态内存。不知道这个是不是有影响，然而既然已经迁移了也就不再追查，就此翻篇了。

« 上一页