k8s系列问题：[ERROR Port-10250]: Port 10250 is in use

原创 于 2024-07-18 10:17:41 发布 · 1.8k 阅读 · 8 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes #容器 

preflight] Some fatal errors occurred:
	[ERROR Port-10250]: Port 10250 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
error execution phase preflight
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	cmd/kubeadm/app/cmd/phases/workflow/runner.go:260

解决方法

  • 在启动命令添加 --ignore-preflight-errors=Port-10250 sudo kubeadm init --config kubeadm-config.yaml --v=5 --ignore-preflight-errors=Port-10250

  • 查看端口是否真的被占用了sudo lsof -i :10250，如果占用了kill -9 pid

  • sudo kubeadm reset

kubernetes搭建过程中错误整理
qq_41619571的博客
02-24 5089
To see the stack trace of this error execute with --v=5 or higher [root@master init]# kubeadm init --dry-run I0224 19:20:48.633116 11505 version.go:251] remote version is much newer: v1.23.4; falling back to: stable-1.17 W0224 19:20:54.451538 11505 v
k8s kubelet 10250监控端口访问配置
最新发布
tingting0119的博客
09-29 520
本文摘要：介绍了Kubernetes监控配置过程，包括修改kubelet配置文件、使用PEM证书测试接口访问（/pods和/metrics）、Prometheus证书转换（PEM转CRT格式）以及RBAC权限配置。详细说明了创建ServiceAccount、ClusterRole和ClusterRoleBinding的YAML配置，生成kubelet访问token，并提供了系统状态检查命令（kubelet服务、防火墙规则、RBAC权限验证和证书有效期检查）。
[kubernetes]k8s主节点初始化报错[ERROR Port-10250]: Port 10250 is in use解决方法
weixin_45457825的博客
06-03 2248
执行 systemctl stop kubelet 命令即可。
kubernetes 初始化报错 /var/lib/etcd is not empty
mry6的博客
03-30 2583
kubernetes 初始化报错 /var/lib/etcd is not empty 问题描述解决问题和原由重新进行初始化 问题描述 在使用kubeadm init出现报错 [ERROR DirAvailable–var-lib-etcd]: /var/lib/etcd is not empty [preflight] Some fatal errors occurred: [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not e
【问题解决】error execution phase preflight: [preflight] Some fatal errors occurred
流氓兔的博客
03-05 1万+
背景 运行kubeadm join 命令加入集群时，报如下错 命令如下 root@zrs:~# kubeadm join 192.168.1.62:6443 --token r6omg1.wf03wzc5a13u7ubi --discovery-token-ca-cert-hash sha256:de0da2432966401f76b217870bc296c5c21b8a059522885c90e7809f5c2d98dd 报错信息 [preflight] Running pre-flight c
[ERROR Port-10250]: Port 10250 is in use
u010779292的博客
06-17 9670
执行:kubeadm join 192.168.118.200:6443 --token brglsa.hs4cqsalc8nh86kl --discova256:dcda322dd0313ab38515b9e602d97ad970877fe2f148a22a763cd7cad1b8fa5e W0617 22:42:55.164981 87321 join.go:346] [preflight] WARNING: JoinControlPan control-plane flag is not ...
k8s报错 [ERROR Port-10257]: Port 10257 is in use
ふりこ细工の心
03-04 2206
k8s kubeadm reset master节点后重新添加时报错 [ERROR Port-10257]: Port 10257 is in use 检查端口占用 [root@k8s-master1 data]# lsof |grep 10257 lsof: WARNING: can't stat() tmpfs file system /data/docker/containers/4707e9dfad67d9abf51459f61b937e5c017a671bd76ea0df7175cf88137
error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR Port-6443]: Port 6443 is in use [ERROR Port-10259]: Port 10259 is in use [ERROR Port-10257]: Port 10257 is in use [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists [ERROR Port-10250]: Port 10250 is in use [ERROR Port-2379]: Port 2379 is in use [ERROR Port-2380]: Port 2380 is in use [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher
06-18
但不推荐，因为标准端口是6443---apiVersion:kubeadm.k8s.io/v1beta3kind:ClusterConfiguration#可以在这里配置其他集群设置，如networking.podSubnet等注意：修改apiserver端口可能会带来其他问题（如需要调整...
k8s重新初始化master节点(初始化master节点报错:Port 6443 is in use)
sun_luming的博客
05-07 1万+
解决方案： 第一步：删除前一次初始化产生的文件及文件夹 rm -rf /etc/kubernetes/* rm -rf ~/.kube/* rm -rf /var/lib/etcd/* 第二步：停用前一次初始化占用的端口 (对照自己的报错提示信息，哪个占用就停哪个，别乱复制粘贴) lsof -i :6443|grep -v "PID"|awk '{print "kill -9",$2}'|sh lsof -i :10250|grep -v "PID"|awk '{print "kill -9",$2}'.
[init] Using Kubernetes version: v1.28.0 [preflight] Running pre-flight checks error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR Port-6443]: Port 6443 is in use [ERROR Port-10259]: Port 10259 is in use [ERROR Port-10257]: Port 10257 is in use [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists [ERROR Port-10250]: Port 10250 is in use [ERROR Port-2379]: Port 2379 is in use [ERROR Port-2380]: Port 2380 is in use [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher
08-09
cat | sudo tee /etc/modules-load.d/k8s.conf overlay br_netfilter EOF ``` ### 3.4 分步初始化并验证控制平面组件状态 在完成预检和清理工作后，可以使用 `kubeadm init` 分步初始化集群。建议使用配置文件方式...
root@root:~# kubeadm init --config ./kubeadm_init.yaml [init] Using Kubernetes version: v1.29.1 [preflight] Running pre-flight checks error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR Port-6443]: Port 6443 is in use [ERROR Port-10259]: Port 10259 is in use [ERROR Port-10257]: Port 10257 is in use [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists [ERROR Port-10250]: Port 10250 is in use [ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist [ERROR Port-2379]: Port 2379 is in use [ERROR Port-2380]: Port 2380 is in use [ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` To see the stack trace of this error execute with --v=5 or higher
03-21
若端口被K8s自身组件占用，可能是残留进程未清理，需执行： ```bash sudo kubeadm reset # 重置集群 sudo systemctl restart kubelet docker # 重启相关服务 ``` #### 2. **文件已存在错误** 若提示`/etc/...
kubeadm join时出现错误：[ERROR Port-10250]: Port 10250 is in use [ERROR FileAvailable--etc-kubernetes-pki
koooooooo5的博客
04-15 1万+
kubeadm join时出现错误：[ERROR Port-10250]: Port 10250 is in use；[ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists 初次使用kubeadm构建k8s集群，所以对子节点加入管理节点的过程认识不足，导致我先对子节点进行了kubeadm init之后，才准备进行kubeadm join操作。结果出现了如下错误： [root@k8s
故障集------------K8S部署出现[ERROR Port-10250]: Port 10250 is in use
一个不愿透露姓名的金先生
08-17 3072
[ERROR Port-10250]: Port 10250 is in use 执行 kubeadm reset 重新配置
k8s 初始化问题 [ERROR Port-10250]: Port 10250 is in use
大胡子
01-10 1561
安裝K8S加入新节点 Port 10250 is in use
wangyibo123ok的博客
07-24 730
在末尾加入一行 --ignore-preflight-errors=Port-10250。
k8s端口被占用:[ERROR FileAvailable--etc-kubernetes-manifests-kub、[ERROR Port-10250]: Port 10250 is in use
Tz.的博客
12-02 2万+
[ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manag...
k8s各组件端口
风向决定发型丶的博客
05-24 4079
10252：kube-controller-manager和kube-apiserver之间的通信端口，用于接收kube-apiserver发送的请求，包括同步cluster state、管理Pod副本数、节点状态等。10251：kube-scheduler和kube-scheduler组件之间的通信端口，用于接收来自kube-apiserver的调度请求，并将调度结果返回给kube-apiserver。10255：kubelet的只读端口，用于提供节点的健康状况以及容器运行时信息的监控数据。
Kubelet 各个端口作用 10250
热门推荐
小楼一夜听春雨，深巷明朝卖杏花
02-10 3万+
--port int32Default: 10250 The port for the kubelet to serve on. (DEPRECATED: This parameter should be set via the config file specified by the kubelet's--configflag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

半山猿

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值