k8s图形界面登录报错Failure

最新推荐文章于 2024-01-21 16:15:08 发布
原创 最新推荐文章于 2024-01-21 16:15:08 发布 · 1k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes #容器 #云原生

本文讲述了在使用k8s图形界面时遇到的登录报错，介绍了如何通过处理证书问题，包括获取client-certificate-data和client-key-data，生成p12文件，并在Chrome和Firefox浏览器中导入证书，从而解决登录问题并实现token登录的过程。

k8s图形界面登录报错如下

{
   
   
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {
   
   
    
  },
  "status": "Failure",
  "message": "forbidden: User \"system:anonymous\" cannot get path
最低0.47元/天 解锁文章
【k8s管理--可视化界面】
嘻哈记的运维学习之路
03-04 3121
kubernetes可视化界面
K8S安装部署保姆级教学(有手就行)+harbor镜像仓库+docker
qq_34794370的博客
11-08 2698
kubernetes、k8s、docker、容器自动化部署
Kubernetes API响应说明
qingdao666666的博客
02-28 3940
API Server响应用户请求时附带一个状态码，该状态码符合HTTP规范。表3.1列出了API Server可能返回的状态码。 状态码 编码 描述 200 ok 表明请求完成 201 Created 表明创建类的请求完全成功 204 NoContent 表明请求完全成功，同时HTTP响应不包含响应体。 在响应OPTIONS方法的...
centos安装kubernets(三) 解决dashboard报错解决
wh0426的专栏
01-13 1万+
访问http://121.201.29.62:8080/ui时报错： { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "no endpoints available for service \"kubernetes-dashboard\"",
k8s做注册中心和负载均衡的时候无法拉取服务列表的问题
ygreatred的博客
03-04 1326
记录一个bug：目前很多服务使用k8s作为注册中心和负载均衡中间件。但是在项目使用中，会出现一个问题。服务运行一段时间之后，会出现无法获取k8s上服务列表的bug，返回403
【k8s】Kubernetes版本v1.17.3 kubesphere 3.1.1 默认用户登录失败
oDianZi1234567的博客
09-11 1544
问题解决日志： 最后reboot 重启。
k8s1.27.2版本二进制高可用集群部署
qq_23191379的博客
01-21 1619
k8s 1.27 二进制部署高可用集群
k8s部署及管理
weixin_48419369的博客
10-28 3747
kubernetes 概述 官网地址：https://kubernetes.io/zh/docs/concepts/overview —kubernetes名字来自希腊语，意思是舵手（领航员），k8s是将k和s之间的8个字母ubernete替换成8的缩写 —Kubernetes的创造者是行业巨头Google —Kubernetes是基于Borg的大规模容器管理的开源版本 —2014年6月Google正式公布并宣布开源 —编配，管理，调度等各方面集成的一套管理容器的系统 —Kubernetes 是一个开源容器
【Devops实践】Git+Gitlab+Jenkins pipeline(maven+Sonarqube+harbor) +k8s 整合CICD
qq707203070的博客
10-31 1472
1.git 提交代码 2.gitlab 存储代码 3.Jenkins pipeline 整合(maven编译代码->Sonarqube代码质量检测->经过代码质量检测后代码构建的容器镜像存到harbor镜像仓库)，将写好的yaml文件传送到K8s master中执行 4.k8s apply -f yaml文件部署deployment
k8s安装可视化界面
啊苏哥哥好的博客
10-24 368
k8s 可视化界面的搭建，以及搭建后设置 token 不用过期的处理
调用Kubernetes API时可能会发现的问题
Docker的专栏
02-23 1831
▲点击上方“分布式实验室”关注公众号回复“1”抽取纸质技术书使用CLI（如curl）或GUI（如postman）HTTP客户端调用Kubernetes API有很多理由。例如，你可能需要...
解决k8s访问报anonymous cannot get path的问题
云深海阔专栏
06-01 1万+
k8s图形界面登录报错如下 { "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "forbidden: User \"system:anonymous\" cannot get path \"/\"", "reason": "Forbidden", "details": { }, "code": 403 } 证书问题，
解决使用json配置文件删除k8s中namespace解析json报错的问题
成の博客
06-02 1897
结果没有什么改变，说明删除namespace不成功，返回查看可能是命令行的问题，文件名使用了字符串，而字符串不是json，即使没有报错，仍然是不生效的，所以准备改为转义字符。最终我决定重新生成json，并重新执行整个删除操作，先查看namespace的状态，如下。可以看到dev是Terminating的状态，可删除，重新生成json再执行。参考github的issue，考虑是json的问题，建议是重新生成。这个状态卡住了半天，再执行远程强制删除的命令，结果冲突了。执行结果，ns没有被删除。
K8S集群安全机制
weixin_45541397的博客
08-27 1007
由于API-Server 是 Kubernetes 集群数据的唯一访问入口，任一 Kubernetes API 的访问都属于以下三种方式之一:以证书方式访问的普通用户或进程，包括运维人员及 kubectl、 kubelet 等进程以 Service Account 方式访问的 Kubernetes 的内部服务进程以匿名方式访问的进程两种用户账号集群内部的 Service-Account，但它并不是给 Kubernetes 集群的用户(系统管理员、 运维人员、租户用户等)用的，而是给运行在 Pod 里的进程用
Kubernetes（k8s）集群渗透
weixin_45253622的博客
08-27 2022
Kubernetes，又称为 k8s，是一种可自动实施Linux容器操作的开源平台，可以帮助用户省去应用容器化过程的许多手动部署和扩展操作，也就是说，它可以将运行 Linux 容器的多组主机聚集在一起并轻松高效地管理这些集群。......
Kubernetes 集群部署–所遇到的问题
happyzwh的专栏
01-11 4378
          查看dashboard界面 访问以下链接（1.8.3访问 https://masterip:6443/ui 无法访问）： https://MasterIP:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ 当然这个链接是怎么来的？ [root@ma...
Kubernetes身份认证和授权操作全攻略：访问控制之Service Account
Rancher
09-06 1053
这是本系列的最后一篇文章，前面我们了解了访问控制中的基本概念以及身份认证和授权的具体操作，本文我们将进一步了解访问控制中的service account。 Kubernetes中有用户和service account的概念，可用于访问资源。用户与密钥和证书相关联用于验证API请求，使用其中一个配置方案对在集群外部发起的任何请求进行身份验证。最常见的方案是通过X.509证书进行身份认证请求。有关创建...
k8s api 接口 401
qq_36270681的博客
03-04 5937
想直接调用https的，没有token就会 [root@k8s-master1 ~]# curl https://10.1.234.100:6443/api/v1/namespaces/default/pods --insecure { "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "pods is forbidden: User \"sy.
【java后端常见问题1】“status“: 404, “error“: “Not Found“, “message“: “No message available“,
热门推荐
weixin_43442778的博客
08-16 2万+
前言 今天和前端一起排查问题，发现一个接口返回的超级慢！最终检查发现是因为ta把一个接口写错了，Get请求出错根本原因处在接口中的参数传递上面，即使用的是Query参数还是Path参数。 Query参数传递接口 这时的Controller参数通常是一个HttpServletRequest，如下面的代码示例： @GetMapping public JSONResult<Object> retrieve(HttpServletRequest request) { .
[root@k8s-master ~]# sudo systemctl daemon-reload [root@k8s-master ~]# sudo systemctl start etcd Job for etcd.service failed because the control process exited with error code. See "systemctl status etcd.service" and "journalctl -xe" for details. [root@k8s-master ~]# journalctl -xe -u etcd 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128033+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128097+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128118+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128132+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12815+0800","caller":"flags/f 5月 26 15:24:04 k8s-master systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128167+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128188+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.1282+0800","caller":"flags/fl 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128214+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128234+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128249+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128261+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128273+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128339+0800","caller":"flags/ 5月 26 15:24:04 k8s-master systemd[1]: Failed to start etcd. -- Subject: Unit etcd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has failed. -- -- The result is failed. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128452+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128517+0800","caller":"etcdma 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128661+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128696+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128765+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"error","ts":"2025-05-26T15:24:04.129386+0800","caller":"embed 5月 26 15:24:04 k8s-master systemd[1]: Unit etcd.service entered failed state. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.129539+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12956+0800","caller":"embed/e 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.129593+0800","caller":"etcdma 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"fatal","ts":"2025-05-26T15:24:04.12962+0800","caller":"etcdma 5月 26 15:24:04 k8s-master systemd[1]: etcd.service failed. lines 1611-1664/1664 (END) 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128033+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128097+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128118+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128132+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12815+0800","caller":"flags/fl 5月 26 15:24:04 k8s-master systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128167+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128188+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.1282+0800","caller":"flags/fla 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128214+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128234+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128249+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128261+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128273+0800","caller":"flags/f 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128339+0800","caller":"flags/f 5月 26 15:24:04 k8s-master systemd[1]: Failed to start etcd. -- Subject: Unit etcd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has failed. -- -- The result is failed. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128452+0800","caller":"embed/c 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128517+0800","caller":"etcdmai 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128661+0800","caller":"embed/c 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128696+0800","caller":"embed/e 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128765+0800","caller":"embed/e 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"error","ts":"2025-05-26T15:24:04.129386+0800","caller":"embed/ 5月 26 15:24:04 k8s-master systemd[1]: Unit etcd.service entered failed state. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.129539+0800","caller":"embed/e 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12956+0800","caller":"embed/et 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.129593+0800","caller":"etcdmai 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"fatal","ts":"2025-05-26T15:24:04.12962+0800","caller":"etcdmai 5月 26 15:24:04 k8s-master systemd[1]: etcd.service failed. ~ lines 1611-1664/1664 (END) 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128033+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128097+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128118+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128132+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12815+0800","call lines 1611-1634/1664 98% 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","caller":"flags/ lines 1611-1629/1664 97% 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128033+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128097+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128118+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128132+0800","cal 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12815+0800","call lines 1611-1634/1664 98% 5月 26 15:24:04 k8s-master systemd[1]: etcd.service holdoff time over, scheduling restart. 5月 26 15:24:04 k8s-master systemd[1]: Stopped etcd. -- Subject: Unit etcd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has finished shutting down. 5月 26 15:24:04 k8s-master systemd[1]: Starting etcd... -- Subject: Unit etcd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has begun starting up. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127562+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127885+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127915+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127936+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.127954+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128017+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128033+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128097+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128118+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128132+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12815+0800","caller":"flags/f 5月 26 15:24:04 k8s-master systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128167+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128188+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.1282+0800","caller":"flags/fl 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128214+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128234+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128249+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128261+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128273+0800","caller":"flags/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128339+0800","caller":"flags/ 5月 26 15:24:04 k8s-master systemd[1]: Failed to start etcd. -- Subject: Unit etcd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit etcd.service has failed. -- -- The result is failed. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128452+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128517+0800","caller":"etcdma 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.128661+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128696+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.128765+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"error","ts":"2025-05-26T15:24:04.129386+0800","caller":"embed 5月 26 15:24:04 k8s-master systemd[1]: Unit etcd.service entered failed state. 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.129539+0800","caller":"embed/ 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"info","ts":"2025-05-26T15:24:04.12956+0800","caller":"embed/e 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"warn","ts":"2025-05-26T15:24:04.129593+0800","caller":"etcdma 5月 26 15:24:04 k8s-master etcd[21322]: {"level":"fatal","ts":"2025-05-26T15:24:04.12962+0800","caller":"etcdma 5月 26 15:24:04 k8s-master systemd[1]: etcd.service failed. lines 1611-1664/1664 (END) 如何解决？
最新发布
05-27
类似于引用[4]描述的情况，在安装图形界面或其他组件过程中改变了系统的默认环境变量或服务链路，从而影响到核心功能模块如网络连接等基础支持层面上的东西。这间接造成了某些后台守护程序比如我们的主角——Etcd不...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

打赏作者

mandarin_meng

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

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

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

打赏作者

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

抵扣说明：

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

余额充值