【Kubernetes】The connection to the server <master>:6443 was refused - did you specify the right host ...

最新推荐文章于 2025-04-08 17:00:53 发布
最新推荐文章于 2025-04-08 17:00:53 发布
阅读量1.7w 收藏 2
点赞数
文章标签： 网络 运维 runtime
原文链接：http://www.cnblogs.com/yuxiaoba/p/9825565.html
版权

　　不知道怎么用着用着，使用kubectl 时报错，错误如下：

root@R740-2-2:~# kubectl get pod
The connection to the server 107.105.136.28:6443 was refused - did you specify the right host or port?
$systemctl status kubelet
Mar 07 20:42:25 server1 kubelet[14619]: E0307 20:42:25.908557 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:26 server1 kubelet[14619]: E0307 20:42:26.718263 14619 eviction_manager.go:238] eviction manager: unexpected err: failed to get node info: node "server1" not found
Mar 07 20:42:26 server1 kubelet[14619]: E0307 20:42:26.906939 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:26 server1 kubelet[14619]: E0307 20:42:26.907933 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:26 server1 kubelet[14619]: E0307 20:42:26.908994 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.392766 14619 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded w
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.392788 14619 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "kube-apiserver-server1_kube-system(7c74aa0f4b9044a62ba3fc2b222b6a49)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: net/http: request c
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.392795 14619 kuberuntime_manager.go:647] createPodSandbox for pod "kube-apiserver-server1_kube-system(7c74aa0f4b9044a62ba3fc2b222b6a49)" failed: rpc error: code = Unknown desc = failed pulling image "gcr.io/google_containers/pause-amd64:3.0": Error response from daemon: Get https://gcr.io/v2/: net/http: request
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.392823 14619 pod_workers.go:186] Error syncing pod 7c74aa0f4b9044a62ba3fc2b222b6a49 ("kube-apiserver-server1_kube-system(7c74aa0f4b9044a62ba3fc2b222b6a49)"), skipping: failed to "CreatePodSandbox" for "kube-apiserver-server1_kube-system(7c74aa0f4b9044a62ba3fc2b222b6a49)" with CreatePodSandboxError: "CreatePodSandbo
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.907221 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.908220 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:27 server1 kubelet[14619]: E0307 20:42:27.909242 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:28 server1 kubelet[14619]: I0307 20:42:28.239272 14619 kubelet_node_status.go:273] Setting node annotation to enable volume controller attach/detach
Mar 07 20:42:28 server1 kubelet[14619]: I0307 20:42:28.246581 14619 kubelet_node_status.go:82] Attempting to register node server1
Mar 07 20:42:28 server1 kubelet[14619]: E0307 20:42:28.246744 14619 kubelet_node_status.go:106] Unable to register node "server1" with API server: Post https://107.105.136.28:6443/api/v1/nodes: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:28 server1 kubelet[14619]: E0307 20:42:28.907491 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:28 server1 kubelet[14619]: E0307 20:42:28.908477 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:28 server1 kubelet[14619]: E0307 20:42:28.909606 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:29 server1 kubelet[14619]: E0307 20:42:29.907804 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:29 server1 kubelet[14619]: E0307 20:42:29.908776 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:29 server1 kubelet[14619]: E0307 20:42:29.909785 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:30 server1 kubelet[14619]: E0307 20:42:30.908131 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:30 server1 kubelet[14619]: E0307 20:42:30.909155 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:30 server1 kubelet[14619]: E0307 20:42:30.910228 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:31 server1 kubelet[14619]: E0307 20:42:31.908495 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Failed to list *v1.Service: Get https://107.105.136.28:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:31 server1 kubelet[14619]: E0307 20:42:31.909392 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://107.105.136.28:6443/api/v1/nodes?fieldSelector=metadata.name%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:31 server1 kubelet[14619]: E0307 20:42:31.910461 14619 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://107.105.136.28:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dserver1&limit=500&resourceVersion=0: dial tcp 107.105.136.28:6443: getsockopt: connection refused
Mar 07 20:42:32 server1 kubelet[14619]: E0307 20:42:32.018611 14619 event.go:209] Unable to write event: 'Patch https://107.105.136.28:6443/api/v1/namespaces/default/events/server1.1519a1c427a76a94: dial tcp 107.105.136.28:6443: getsockopt: connection refused' (may retry after sleeping)

　　6443是Kubernetes集群APIServer的端口，因此猜测是APIServer挂掉了，因此查看正在运行的进程

$ps -aux | grep "kube"

　　发现果然没有有关的进程，因此重启相关的服务

$systemctl restart kube-apiserver
$systemctl restart kube-controller-manager
$systemctl restart kube-scheduler

　　查看状态，可以使用kubectl命令了

root@R740-2-3:~# kubectl get componentstatus
NAME                 STATUS    MESSAGE             ERROR
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-2               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}

　

转载于:https://www.cnblogs.com/yuxiaoba/p/9825565.html

K8S报错：The connection to the server localhost:8080 was refused - did you specify the right host......
博客主要分享技术教程、工具教程、bug解决、前沿技术动态、编程经验、心得感悟等。 内容同步、干货获取、推广宣发请看侧栏推广信息
12-12 486
每个人都有惰性，但不断学习是好好生活的根本，共勉！
The connection to the server localhost:8080 was refused - did you specify the right host or port?k8s
qq_29700227的博客
08-25 1206
关于k8s类似于：The connection to the server localhost:8080 was refused - did you specify the right host or port?的toubleshooting
记录一次kubectl报错：The connection to the server IP:6443 was refused - did you specify the right host or p
weixin_65176861的博客
04-03 1667
首先，由于某种原因（可能与网络或服务状态有关），控制器对该 API 组进行了速率限制重排队。随后，在尝试加载该 API 组的 OpenAPI 规范时，收到了 503 Service Unavailable 的 HTTP 错误响应，表明相关服务暂时无法提供服务。同时，处理请求的代码在上下文中找不到必要的 RequestInfo，可能导致请求处理出现异常。那就只能怀疑事docker配置问题了，昨天配置了镜像源，怀疑是这个问题。先看看一些防火墙，swap等配置是不是把6443搞了。查找docoker info。
K8S 问题“The connection to the server....:6443 was refused - did you specify the right host or port?
Thomson_tian的博客
03-29 1577
https://blog.csdn.net/yujia_666/article/details/114118291
The connection to the server 192.168.1.111:6443 was refused - did you specify the right host or port
最新发布
qq_42703153的博客
04-08 420
kubectl命令无法使用的其中一个可能的解决办法。
解决方案：[“The connection to the server ip:6443 was refused - did you specify the right host or port“]
一切有为法，如梦亦如幻，如露亦如电，应作如是观。
12-26 6601
1、k8s有时候会报错The connection to the server ip:6443 was refused - did you specify the right host or port ，本文档提供几种可能产生该报错的原因和排障思路。
The connection to the server ip:6443 was refused - did you specify the right host or port
爱死亡机器人
12-14 1万+
解决方法1： #!/bin/bash swapoff -a systemctl start kubelet docker start (docker ps -a -q) docker start (docker ps -a -q) 解决方法2： master： 192.168.211.40 node1： 192.168.211.41 node2： 192.168.211.42 master $ kubeadm reset $ kubeadm init --pod-network-cidr=192.1
The connection to the server localhost:6443 was refused - did you specify the right host or port?
weixin_51513710的博客
04-14 519
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Kubectl指令报错：The connection to the server 127.0.0.1:6443 was refused - did you specify the right host
weixin_45056021的博客
10-12 797
Kubectl指令报错：The connection to the server 127.0.0.1:6443 was refused - did you specify the right host。解决方案，kubernetes的认证文件没在环境变量中，尤其是k3s安装时不会自动拷贝到常用路径。
The connection to the server master:6443 was refused - did you specify the right host or port?
qq_41054648的博客
10-19 5392
The connection to the server master:6443 was refused - did you specify the right host or port?kubernetes（版本1.6）安装好后第2次启动会报上面的错误（kubectl get pod --all-namespaces，经过查看日志发现了错误根源在于K8S v1.6.x的一个变化，文件驱动默认由s...
k8s集群不可用：The connection to the server 192.168.117.161:6443 was refused - did you specify the right h...
全栈测试笔记
08-15 1024
虚拟机非正常关机后，k8s集群不可用 获取节点，报如下错，kubectl get node 查看env：env | grep -i kubernetes 查看docker状态：systemctl status docker 查看kubelet状态：systemctl status kubelet 查看监听端口：netstat -pnlt | grep 6443 如果监听端口不在，可以看...
k8s--重启后报错：The connection to the server lb.kubesphere.local:6443 was refused - did you specify the r
qq_43470725的博客
11-21 4564
k8s
The connection to the server lb.kubesphere.local:6443 was refused - did you specify the right host..
weixin_50135832的博客
06-09 1812
问题的描述：今天通过安装了一下kubesphere,安装成功之后，关机重启了一下，就出现了问题。无法启动k8s和kubespheredocker启动没有问题，但是里面所有的镜像都没有运行起来。抓去了一下主要的错误信息这个错误表明kubelet配置使用的cgroup驱动是systemd，而Docker使用的cgroup驱动是cgroupfs。Kubernetes和Docker必须使用相同的cgroup驱动才能正常工作，否则可能导致资源管理和隔离的问题。
反复出现：The connection to the server x..x:6443 was refused - did you specify the right host or
qq_38359135的博客
10-12 8442
在所有节点重启kubelet试试： sudo systemctl restart kubelet.service
The connection to the server ip:6443 was refused - did you specify the right host or port?重启了虚拟机之后
qq_39605670的博客
12-03 1390
VM虚拟机安装k8s，重启虚拟机之后连接k8s拒绝 环境：centos7 前提：已经设置静态ip 原因：查看master主机的k8s容器是否启动 发现： [root@master k8s-deployment]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES [root@master
kubernetes/k8s重启实体服务器后集群启动异常The connection to the server xxx:6443 was refused - did you specify...
qq_33342132的博客
01-21 1334
例如：项目场景：示例:通过蓝牙芯片(HC-05)与手机 APP 通信，每隔 5s 传输一批传感器数据(不是很大)
[kubernetes/出错] kubectl 返回 The connection to the server 192.168.X.X:6443 was refused
mathemagics的博客
09-14 897
快速解决方法：重启
问题“The connection to the server....:6443 was refused - did you specify the right host or port?”的处理！
热门推荐
sinat_28371057的博客
11-21 4万+
问题“The connection to the server <master>:6443 was refused - did you specify the right host or port?”的处理！ 一、故障产生 在不关闭kubernets相关服务的情况下，对kubernets的master节点进行重启。（模拟服务器的异常掉电） 二、故障状况 启动后无法远程到kubernets的dashbaord，后进行如下命令报错。 # kubectl get nodes T...
The connection to the server 10.10.0.2:6443 was refused - did you specify the right host or port?
qq_39545674的博客
12-03 1万+
当重启k8s的master后，我遇到了不可想象的神秘错误： The connection to the server 10.10.0.2:6443 was refused - did you specify the right host or port? 方案1 去百度了一下，绝大多数的解决方案是： swapoff -a vim /etc/fstab # 然后注释掉有 swaq 的那一行 # 再重启 reboot 这样做是因为k8s需要关闭swap 我照做了，但是没有效果 方案2 后来
The connection to the server 192.168.0.60:6443 was refused - did you specify the right host or port?
08-21
在安装Kubernetes时，需要在master节点的/etc/hosts文件中添加相应的主机名和IP地址映射关系。可以使用以下命令将这些信息添加到/etc/hosts文件中： ``` cat >> /etc/hosts << EOF 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 172.31.0.60 k8s-master 172.31.0.224 k8s-node01 172.31.0.237 k8s-node02 EOF ``` 在安装Kubernetes的过程中，还需要安装Docker、kubeadm和kubelet。这些软件需要在所有节点上安装。 在访问Kubernetes集群的地址时，需要使用公网IP，并且端口是随机生成的。可以使用`kubectl get svc`命令获取访问地址。在安全组中，需要配置允许该端口的入方向访问。访问地址的格式为：`http://NodeIP:Port`。[2] 如果在使用`kubectl get pod`命令时，pod一直处于"ContainerCreating"状态，可以通过`kubectl describe pod <nginx-pod-name>`命令查看日志，可能会得到以下报错信息： ``` stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/ ``` 解决办法是创建该目录和文件，并将本机IP写入nodename文件中： ``` mkdir /var/lib/calico/ touch /var/lib/calico/nodename echo "172.31.0.60" > /var/lib/calico/nodename ``` 然后重新验证port工作是否正常，可以使用`kubectl get pod`命令查看nginx的pod状态。 如果需要验证Pod之间的网络通信是否正常，可以使用`kubectl get pods -o wide`命令查看pod的IP地址，然后在所有节点上使用ping命令进行验证。 如果需要验证DNS解析是否正常，可以使用`kubectl get pods -n kube-system`命令查看coredns的状态。 在安装完Kubernetes后，可以部署Dashboard来方便地管理和监控集群。具体部署方式可以根据文档进行操作。 根据您提供的错误信息"The connection to the server 192.168.0.60:6443 was refused - did you specify the right host or port?"，可能是因为指定的主机或端口不正确。请确保您在访问Kubernetes集群时使用的主机和端口是正确的。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* *2* *3* [kubernetes 1.20.0安装](https://blog.csdn.net/weixin_43872526/article/details/123611518)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 100%"] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值