kubectl命令出现：Unable to connect to the server: dial tcp 192.168.0.106:6443: i/o timeout

最新推荐文章于 2024-03-18 10:56:17 发布
原创 最新推荐文章于 2024-03-18 10:56:17 发布 · 3.1w 阅读 · 6 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes #docker

本文介绍如何在机器重启后遇到kubectl连接服务器超时的问题，通过创建kubeconfig文件、复制admin.conf并调整权限，以及重启dashboard代理，提供步骤解决方法。

机器重启后，输入kubectl命令，会出现报错的提示：Unable to connect to the server: dial tcp 192.168.0.106:6443: i/o timeout

经过多次试验，发现，重新执行以下就可以了：

  1. $ mkdir -p $HOME/.kube
  2. $ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  3. $ sudo chown $(id -u):$(id -g) $HOME/.kube/config

再重启一下dashboard：kubectl proxy --address='0.0.0.0'  --accept-hosts='^*$' &

kubectl get 报错：kubectl Unable to connect to the server: dial tcp 10.12.2.199:6443: i/o timeout
专注基础架构领域
06-05 1万+
具体输出如下： 场景：高可用集群 master 节点，当我执行：kubectl get nodes，出现如下错误： kubectl Unable to connect to the server: dial tcp 10.12.2.199:6443: i/o timeout 原因是 Master 节点初始化集群的时候，没有执行： $ mkdir -p $HOME/.kube $ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/confi
【ubutnu24.04】k8s部署3:重新安装1.31.0并init成功
突围
08-15 1039
#!/bin/sh sudo systemctl restart containerd sudo systemctl status containerd
kubectl命令报错：Unable to connect to the server: dial tcp XXX:16443: connect: no route to host
我是小bā吖的博客
04-13 1万+
刚开始爆出的错误是这个，一看这个IP就不是我当初创建集群时的IP，而是一个阿里云公网IP，其实进入config文件中修改成自己集群的IP就可以了。保存退出后再次查看节点状态，kubectl命令就可以正常使用了。kubernetes集群好久不用了，今天打开集群执行一个。，而这里显然不是，将IP修改为。出现这个问题几种原因，
kubesphpe单机集群删除以及重建
u010674101的专栏
09-09 1855
今天重启了一下，服务器，结果发现昨天部署的k8s环境无法正常使用了。。看来单机版本还是适合开发环境。重启服务器后没有可以到达k8s服务的路由了，iptables规则已经被清空。 [root@k8s-test ~]# kubectl get pvc --all-namespaces Unable to connect to the server: dial tcp: lookup lb.kubesphere.local on 202.96.128.86:53: no such host [root@k8s-
Unable to connect to the server: dial tcp 10.xxx:6443: i/o timeout
weixin_46519031的博客
03-18 682
更改完之后，再次执行。
k8s报错Unable to connect to the server: dial tcp: lookup cluster-endpoint on xxx
qq_38838006的博客
02-19 3941
在此要强调一点的是，直接修改/etc/resolv.conf这个文件是没用的，网络服务重启以后会根据/etc/sysconfig /network-scripts/ifcfg-eth0来重载配置，如果ifcfg-eth0没有配置DNS，那么resolv.conf会被冲掉，重新变成空值。/etc/sysconfig /network-scripts/ifcfg-eth0 下的dns IP。然后使用如下命令重启网络服务。改为 8.8.8.8。
kubesphere-- Unable to connect to the server: dial tcp 192.168.211.182:6443: no route to host
淮水竹亭
06-04 1936
查看kubesphere相关配置文件，显示注册的是192.168.211.182地址，此外虚拟机的IP为192.168.211.130。这次可以将虚拟机网络配置成静态路由，保证路由ip不再变化，以免连接不上。最近鼓捣kubesphere单节点安装，部署服务，使用流水线用的好好的，有两次重启服务器突然显示kubesphere连接不上。这次安装kubesphere，使用的虚拟机ip地址192.168.211.130，不再是动态ip地址。先凑合着用，后面再来填坑。命令，显示kubectl不可用，缺少路由。
Kubectl : Unable to connect to the server : dial tcp 192.168.214.136:6443: connect: no route to host
Asssshzy的博客
01-14 1161
关闭所有与vmvare有关的进程，重启电脑，再次启动虚拟机，ok!
k8s dial tcp connect: no route to host
qq_15138049的博客
11-19 6699
莫名其妙遇到…pod container 启动失败：Back-off restarting failed container [root@hadoop03 k8s]# kubectl get pod -n nfs-client NAME READY STATUS RESTARTS AGE nfs-client-provisioner-764f44f754-gww47 0/1 Cr
腾讯云frp连接失败。login to server failed: dial tcp x:7000: connectex: A connection attempt failed because
热门推荐
lsllll44的博客
01-26 8万+
地址：https://github.com/fatedier/frp 简介：一个高效的反向代理：A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet. 最全面的官方教程文档：https://gofrp.org 自我记录： a、使用TCP代理，开启本地服务器的访问。 Linux服务器启动 frps 命令：nohup ./frps -c frps.ini（无挂起启动命令。可以
read tcp :49560->:9092: i/o timeout under sarama kafka golang panic
mmgithub123的博客
01-29 2119
我们经常出现这个问题，除了上次修复完后，正常跑也总有这种问题。因为我们的场景是文件扫描，文件扫描的处理方式是很重的，消费时间长。所以经常触发重平衡。 那么又回到了原始问题。第一性原理，运维和架构，就是要做工程上的最佳实践，而不是什么技术新旧。最佳实践就是最佳适配。 kafka的consumer重平衡机制，注定了它不适合做长逻辑耗时业务的处理。(它的背景本身是无逻辑处理，只是传输日志) ----...
guyue@k8s-worker01:~$ # 停止所有服务 sudo systemctl stop kubelet sudo systemctl stop cri-docker.service sudo systemctl stop containerd sudo systemctl stop docker # 彻底清理 kubeadm 配置 sudo kubeadm reset --force --cri-socket unix:///var/run/cri-dockerd.sock # 手动删除所有残留配置 sudo rm -rf /etc/kubernetes/* sudo rm -rf /var/lib/kubelet/* sudo rm -rf /var/lib/etcd/* sudo rm -rf /etc/cni/net.d/* # 清理 iptables 规则 sudo iptables -F sudo iptables -t nat -F sudo iptables -t mangle -F sudo iptables -t raw -F sudo systemctl daemon-reload default | xargs -r sudo ip netns delete Stopping 'docker.service', but its triggering units are still active: docker.socket [preflight] Running pre-flight checks W1202 13:26:55.625312 40333 removeetcdmember.go:106] [reset] No kubeadm config, using etcd pod spec to get data directory [reset] Deleted contents of the etcd data directory: /var/lib/etcd [reset] Stopping the kubelet service [reset] Unmounting mounted directories in "/var/lib/kubelet" W1202 13:26:55.768797 40333 cleanupnode.go:99] [reset] Failed to remove containers: output: E1202 13:26:55.763484 40339 remote_runtime.go:277] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" filter="&PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},}" time="2025-12-02T13:26:55+08:00" level=fatal msg="listing pod sandboxes: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" , error: exit status 1 [reset] Deleting contents of directories: [/etc/kubernetes/manifests /var/lib/kubelet /etc/kubernetes/pki] [reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf] The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d The reset process does not reset or clean up iptables rules or IPVS tables. If you wish to reset iptables, you must do so manually by using the "iptables" command. If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar) to reset your system's IPVS tables. The reset process does not clean your kubeconfig files and you must remove them manually. Please, check the contents of the $HOME/.kube/config file. guyue@k8s-worker01:~$ # 创建专用的 kubelet 配置目录 sudo mkdir -p /etc/systemd/system/kubelet.service.d/ # 创建正确的配置文件（使用 .conf 后缀） sudo tee /etc/systemd/system/kubelet.service.d/10-kubeadm.conf <<EOF [Service] Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml" Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9 --v=2" EOF # 重新加载 systemd 配置 sudo systemctl daemon-reload # 验证配置 sudo systemctl cat kubelet [Service] Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml" Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9 --v=2" # /usr/lib/systemd/system/kubelet.service [Unit] Description=kubelet: The Kubernetes Node Agent Documentation=https://kubernetes.io/docs/home/ Wants=network-online.target After=network-online.target [Service] ExecStart=/usr/bin/kubelet Restart=always StartLimitInterval=0 RestartSec=10 [Install] WantedBy=multi-user.target # /etc/systemd/system/kubelet.service.d/0-containerd.conf [Service] Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri> lines 1-20 [4]+ 已停止 sudo systemctl cat kubelet guyue@k8s-worker01:~$ # 创建或覆盖 /etc/default/kubelet（最高优先级配置） echo 'KUBELET_EXTRA_ARGS="--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9"' | sudo tee /etc/default/kubelet # 启动 cri-dockerd sudo systemctl start cri-docker.service sudo systemctl enable cri-docker.service # 验证 CRI 连接 sudo crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock version sudo crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock info KUBELET_EXTRA_ARGS="--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9" Version: 0.1.0 RuntimeName: docker RuntimeVersion: 29.0.0 RuntimeApiVersion: v1 { "status": { "conditions": [ { "type": "RuntimeReady", "status": true, "reason": "", "message": "" }, { "type": "NetworkReady", "status": false, "reason": "NetworkPluginNotReady", "message": "docker: network plugin is not ready: cni config uninitialized" } ] }, "config": { "sandboxImage": "registry.aliyuncs.com/google_containers/pause:3.10.1" } } guyue@k8s-worker01:~$ # 启动 kubelet sudo systemctl start kubelet sudo systemctl enable kubelet # 监控日志（在新终端中运行） sudo journalctl -u kubelet -f --since "now" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069109 40971 server.go:467] "Kubelet version" kubeletVersion="v1.28.2" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069243 40971 server.go:469] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069532 40971 server.go:630] "Standalone mode, no API client" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: E1202 13:27:38.073889 40971 run.go:74] "command failed" err="failed to run Kubelet: validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService" 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Failed with result 'exit-code'. 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Consumed 1.915s CPU time, 7.0M memory peak, 0B memory swap peak. 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 42. 12月 02 13:27:48 k8s-worker01 systemd[1]: Started kubelet.service - kubelet: The Kubernetes Node Agent. 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.478732 41091 server.go:467] "Kubelet version" kubeletVersion="v1.28.2" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.478879 41091 server.go:469] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.479651 41091 server.go:630] "Standalone mode, no API client" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: E1202 13:27:48.485767 41091 run.go:74] "command failed" err="failed to run Kubelet: validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService" 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Failed with result 'exit-code'. ^Z [5]+ 已停止 sudo journalctl -u kubelet -f --since "now" guyue@k8s-worker01:~$ # 在确认 kubelet 正常运行后（看到类似 "Starting to listen on 0.0.0.0:10250" 的日志） sudo kubeadm join 192.168.130.129:6443 \ --token h0epjb.94zz1xhekvf7nfzx \ --discovery-token-ca-cert-hash sha256:a7760aa4d05b6bf0af6be91267c86417999c998318bfe4a8afcb62b757b8f808 \ --cri-socket unix:///var/run/cri-dockerd.sock \ --ignore-preflight-errors=all [preflight] Running pre-flight checks [preflight] Reading configuration from the cluster... [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml' [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet-start] Starting the kubelet [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap... [kubelet-check] Initial timeout of 40s passed. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
最新发布
12-03
apiServerEndpoint: 192.168.130.129:6443 token: <正确token> caCertHashes: - sha256:位哈希值> # 注意这里是完整的64位哈希 nodeRegistration: criSocket: unix:///var/run/cri-dockerd.sock ``` 5. ...
Unable to connect to the server: dial tcp 192.168.0.132:16443: connect: no route to host解决
ZYK213的博客
10-10 1万+
项目场景： vmware部署k8s集群，用于学习。挂起vm后重新启动，执行任何命令都报如下提示： Unable to connect to the server: dial tcp 192.168.0.132:16443: connect: no route to host 查询显卡信息，发现虚拟ip：132未生效： ip a s ens33 2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
【Kubernetes】Error: Unable to connect to the server: dial tcp XXX: connect: no route
Maple的博客
01-09 4万+
1. 问题： 在Kubernetes使用过程中有时出现如下问题，在StackOverfolow上没有找到好的办法，目前能找到的最好办法就是Kubernetes reset。 Unable to connect to the server: dial tcp XXX: connect: no route cni not initialized 2.解决措施： sudo kubeadm...
配置k8s遇到unable to connect to the server：dial tcp 192.168.*.*:5443:connect:no route to host
qq_45751902的博客
10-13 6642
** 配置k8s遇到unable to connect to the server：dial tcp 192.168..:5443:connect:no route to host ** 问题描述 解决后 解决方法 查看192.168.0.106是不是你集群的ip，如果不是，找到一个匹配的文件（红圈内的），然后重做此步，就解决了。 ...
Harbor报错：dial tcp 127.0.0.1:1514: connect: connection refused 解决
何宇泽
12-07 1万+
今天重启harbor，报错信息如下： [root@harbor harbor]# docker-compose up -d harbor-log is up-to-date Starting harbor-portal ... error Starting registry ... Starting redis ... Starting registryctl ... Starting redis ... error ERROR: for harbo
kubectl安装calico：Unable to connect to the server: x509: certificate has expired or is not yet valid
qq_42449963的博客
10-29 1148
在k8s安装的时候需要安装，我们就执行命令安装，但是一直提示： 然后我通过在网上找到的命令更新了k8s证书，并且通过命令发现证书都没有过期，如下： 然后通过k8s安装calico失败这篇文档中了解到可以先将下载下来，但是我发现通过curl命令下载也会提示我证书问题，如下： 所以我就先通过浏览器访问https://docs.projectcalico.org/manifests/calico.yaml，然后把页面内容全部复制到文件中，然后把文件传到虚拟机上就可以了，之后就可以直接通过安装了由于该网址访问很慢，
k8s Unable to connect to the server: EOF 问题解决
weixin_42710740的博客
02-23 7902
原因是K8s 没有启动成功 如下状态方位，启动成功 启动失败的原因多数是镜像下载失败 找到 Docker 的设置页面，在Docker Engine页面，将镜像网站的地址加入到右侧配置文件的registry-mirrors节点下面，这里我使用的是 Docker 官方和中科大的镜像网站地址，你可以依据自己的喜好选择，调整完成之后重启 Dokcer 即可 { "registry-mirrors": [ "https://docker.mirrors.ustc.edu.cn",// 中科...
Unable to connect to the server: dial tcp :x.x.x.x:6449 connect: no route to host
小树苗
04-08 3025
k8s master执行kubectl get 报错如标题 原因是虚拟机IP更换了，重新修改kubeadm-config.yaml文件中advertiseAddress 对应的IP并初始化即可，相当于重新部署，比较麻烦，最好是修改成原来的IP
kubectl get po -n kube-system Unable to connect to the server: dial tcp 192.168.88.138:6443: connect: no route to host
08-01
Unable to connect to server: dial tcp 192.168.88.138:6443: connect: no route to host ``` 该错误表明客户端无法连接到 Kubernetes API Server（运行在 `192.168.88.138:6443`），可能的原因包括网络配置问题、...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值