11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.108952     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.209293     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.310543     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.411121     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.511949     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.612822     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.713249     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.781263     974 controller.go:144] failed to ensure lease exists, will retry in 7s, error: leases.coordination.k8s.io "localhost.localdomain" is forbidden: User "system:node:k8s222" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-node-lease": can only access node lease with the same name as the requesting node
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.813355     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"
11月 05 10:58:35 localhost.localdomain kubelet[974]: E1105 10:58:35.913495     974 kubelet.go:2412] "Error getting node" err="node \"localhost.localdomain\" not found"

1.1 该节点一直NotReady

[root@crust-m01 ~]# kubectl get node
NAME        STATUS     ROLES                  AGE   VERSION
k8s220   NotReady   control-plane,master   44d   v1.21.3
k8s221   NotReady   <none>                 44d   v1.21.3
k8s222   NotReady   <none>                 44d   v1.21.3

1.2 查看该节点详细信息

[root@localhost ~]# kubectl describe node k8s221

……
Unschedulable:      false
Lease:HolderIdentity:  k8s221AcquireTime:     <unset>RenewTime:       Tue, 28 Sep 2021 14:37:08 +0800
Conditions:Type             Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message----             ------    -----------------                 ------------------                ------              -------MemoryPressure   Unknown   Tue, 28 Sep 2021 14:32:16 +0800   Tue, 28 Sep 2021 14:38:17 +0800   NodeStatusUnknown   Kubelet stopped posting node status.DiskPressure     Unknown   Tue, 28 Sep 2021 14:32:16 +0800   Tue, 28 Sep 2021 14:38:17 +0800   NodeStatusUnknown   Kubelet stopped posting node status.PIDPressure      Unknown   Tue, 28 Sep 2021 14:32:16 +0800   Tue, 28 Sep 2021 14:38:17 +0800   NodeStatusUnknown   Kubelet stopped posting node status.Ready            Unknown   Tue, 28 Sep 2021 14:32:16 +0800   Tue, 28 Sep 2021 14:38:17 +0800   NodeStatusUnknown   Kubelet stopped posting node status.
……

1.3 该节点上查看kubelet日志

[root@crust-m2 ~]# service kubelet status -l
Redirecting to /bin/systemctl status  -l kubelet.service
● kubelet.service - kubelet: The Kubernetes Node AgentLoaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)Drop-In: /usr/lib/systemd/system/kubelet.service.d└─10-kubeadm.confActive: active (running) since 二 2021-09-28 14:51:57 CST; 4min 6s agoDocs: https://kubernetes.io/docs/Main PID: 21165 (kubelet)Tasks: 19Memory: 43.0MCGroup: /system.slice/kubelet.service└─21165 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --network-plugin=cni --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.4.19月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.119645   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.220694   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.321635   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.385100   21165 eviction_manager.go:255] "Eviction manager: failed to get summary stats" err="failed to get node info: node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.422387   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.523341   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.624021   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.724418   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.825475   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"
9月 28 14:56:03 crust-m2 kubelet[21165]: E0928 14:56:03.926199   21165 kubelet.go:2291] "Error getting node" err="node \"crust-m2\" not found"

2. 【排错】

1.3中日志输出的启动命令如下

/usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --network-plugin=cni --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.4.1

查看并分析启动命令中所有配置文件都没有问题

发现1.3 中输出的错误err="node \"localhost.localdomain\" not found
而master上 kubectl get node 的信息三个node是 k8s220，k8s221，k8s222
结论
之前安装kubernetes的时候，master的名字是 k8s220，node是k8s221，k8s222，因为 /etc/hostname 中默认写成了 localhost.localdomain，因此kubelet一直报错

3. 【修改】

修改hostname文件，并执行hostname命令修改服务器名称
重启kubelete

node节点kubelet报错 node \“xxxxx“ not found相关推荐

forever保护node server进程报错(node:8156) Warning: Accessing non-existent property ‘padLevels‘ of module e
在运行forever进程 forever start index.js的时候会报错 (node:8156) Warning: Accessing non-existent property 'pad ...
master节点重置后添加node报错_企业实战（23）基于Docker平台的Jenkins添加node节点与报错详解（2）...
相关文章企业实战(23)基于Docker平台部署Jenkins中国定制版(1) 添加node节点前配置在这里插入图片描述在这里插入图片描述开始添加node节点在这里插入图片描述在这里插入 ...
解决kubelet报错：kubelet.go:2183] node “k8s-20-52“ not found
解决kubelet报错:kubelet.go:2183] node "k8s-20-52" not found 由于公司机房服务器重启,k8s其中一个node节点的状态一直为Not ...
java 带密码连接redis 单节点/集群 No reachable node in cluster报错解决
java 带密码连接redis 单节点/集群 No reachable node in cluster报错解决 maven依赖 <dependency><groupId>red ...
eslint检测node 内部模块报错解决方案
如上图所示,eslint检测node 内部模块报错解决, 解决方案: 代码: module.exports = {"env": {"browser": true ...
HTML-CSS-JS Prettify报错Node.js was not found 解决方法
HTML-CSS-JS Prettify报错Node.js was not found sublime编辑器安装的插件prettify,可以格式化js css html非常好用,但是装完之后总是提示N ...
使用docker-compose 启动emqx报错： Erlang closed the connection 查看状态报错 Node ‘emq@.’ not responding to pings
使用docker-compose 启动emqx报错: Erlang closed the connection 查看状态报错 Node 'emq@192.168..' not responding t ...
k8s的kubelet报错PLEG is not healthy: pleg was last seen active 3m41.603110188s ago
kubelet报错日志原因一 k8s集群中存在大量状态为Terminating的Pod 解决 NAMESPACE=devops-test rancher kubectl get pod -n ${N ...
mpi tcp连接报错_MPI分布式编程 --3.OpenMPI多节点运行报错
1. OpenMPI多节点运行报错问题问题描述:节点一即host3,通过mpirun调用节点二即host4的mpi程序,报错如下. $ mpirun -np 1 --host host4 ./mai ...

node节点kubelet报错 node \“xxxxx“ not found

1.1 该节点一直NotReady

1.2 查看该节点详细信息

2. 【排错】

3. 【修改】

node节点kubelet报错 node \“xxxxx“ not found相关推荐

最新文章

热门文章