- 已编辑
创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。
操作系统信息
例如：虚拟机，Centos7.6/8C/16G
Kubernetes版本信息
将 kubectl version 命令执行结果贴在下方
Client Version: version.Info{Major:“1”, Minor:“22”, GitVersion:“v1.22.12”, GitCommit:“b058e1760c79f46a834ba59bd7a3486ecf28237d”, GitTreeState:“clean”, BuildDate:“2022-07-13T14:59:18Z”, GoVersion:“go1.16.15”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“22”, GitVersion:“v1.22.12”, GitCommit:“b058e1760c79f46a834ba59bd7a3486ecf28237d”, GitTreeState:“clean”, BuildDate:“2022-07-13T14:53:39Z”, GoVersion:“go1.16.15”, Compiler:“gc”, Platform:“linux/amd64”}
容器运行时
将 docker version / crictl version / nerdctl version 结果贴在下方
Client: Docker Engine - Community
Version: 26.1.4
API version: 1.45
Go version: go1.21.11
Git commit: 5650f9b
Built: Wed Jun 5 11:32:04 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 26.1.4
API version: 1.45 (minimum version 1.24)
Go version: go1.21.11
Git commit: de5c9cf
Built: Wed Jun 5 11:31:02 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.33
GitCommit: d2d58213f83a351ca8f528a95fbd145f5654e957
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
KubeSphere版本信息
例如：v3.4.1。在线安装。在使用kk安装。
问题是什么
使用了快半年了吧，今天把服务器重启了，内部的apiserver启动的时候提示连接redis超时，redis是内置的服务。不明白为什么。
第一次安装就出现超时，怎么解决啊
kubesphere-monitoring-system prometheus-operator-8955bbd98-wv5lw 2/2 Running 0 24m
kubesphere-system ks-apiserver-86768d4ffb-d2lgp 0/1 CrashLoopBackOff 4 (70s ago) 25m
kubesphere-system ks-apiserver-86768d4ffb-mwb4l 0/1 CrashLoopBackOff 4 (62s ago) 25m
kubesphere-system ks-apiserver-86768d4ffb-sv2gp 0/1 CrashLoopBackOff 4 (74s ago) 25m
kubesphere-system ks-console-85c97b6d7d-hqg6t 1/1 Running 0 25m
kubesphere-system ks-console-85c97b6d7d-k7sw9 1/1 Running 0 25m
kubesphere-system ks-console-85c97b6d7d-ng9cg 1/1 Running 0 25m
kubesphere-system ks-controller-manager-7b5857f957-q8qsw 1/1 Running 0 25m
kubesphere-system ks-controller-manager-7b5857f957-tg9np 1/1 Running 0 25m
kubesphere-system ks-controller-manager-7b5857f957-zqth5 1/1 Running 0 25m
kubesphere-system ks-installer-5594ffc86d-256kr 1/1 Running 1 (10m ago) 29m
kubesphere-system redis-68d7fd7b96-gvdd9 1/1 Running 0 27m
[root@test-master3 opt]# kubectl logs -f ks-apiserver-86768d4ffb-d2lgp -n kubesphere-system
W0425 01:47:23.992355 1 client_config.go:618] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W0425 01:47:23.993300 1 client_config.go:618] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W0425 01:47:24.003208 1 metricsserver.go:238] Metrics API not available.
E0425 01:47:29.004367 1 cache.go:69] failed to create cache, error: dial tcp 10.233.51.158:6379: i/o timeout
E0425 01:47:29.004445 1 run.go:74] “command failed” err=“failed to create cache, error: dial tcp 10.233.51.158:6379: i/o timeout”
