openshift启动失败
2024-07-04 05:02:39
问题描述：
kube-apiserver自检没有通过，检查发现端口8443没有监听
[root@openshift openshift]# oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
error: did not detect an --insecure-registry argument on the Docker daemon
[root@openshift openshift]# oc cluster up --skip-registry-check=true
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0629 03:24:23.893461 51057 flags.go:30] Running "create-kubelet-flags"
I0629 03:24:24.226490 51057 run_kubelet.go:49] Running "start-kubelet"
I0629 03:24:24.390056 51057 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0629 03:29:24.392998 51057 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
[root@openshift openshift]#
Socket error Event: 32 Error: 10053.
Connection closing...Socket close.Connection closed by foreign host.Disconnected from remote host(centOS) at 18:38:11.
[root@openshift openshift]# oc cluster up --skip-registry-check=true
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0629 03:47:17.628873 39759 config.go:40] Running "create-master-config"
I0629 03:47:24.909524 39759 config.go:46] Running "create-node-config"
I0629 03:47:28.147522 39759 flags.go:30] Running "create-kubelet-flags"
I0629 03:47:28.693783 39759 run_kubelet.go:49] Running "start-kubelet"
I0629 03:47:28.844126 39759 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0629 03:52:45.569132 39759 run_self_hosted.go:571] API server error: an error on the server ("[+]ping ok\n[+]log ok\n[+]etcd ok\n[+]poststarthook/generic-apiserver-start-informers ok\n[+]poststarthook/start-apiextensions-informers ok\n[+]poststarthook/start-apiextensions-controllers ok\n[-]poststarthook/bootstrap-controller failed: reason withheld\n[-]poststarthook/rbac/bootstrap-roles failed: reason withheld\n[-]poststarthook/scheduling/bootstrap-system-priority-classes failed: reason withheld\n[-]poststarthook/ca-registration failed: reason withheld\n[+]poststarthook/start-kube-apiserver-informers ok\n[+]poststarthook/start-kube-apiserver-admission-initializer ok\n[+]poststarthook/quota.openshift.io-clusterquotamapping ok\n[+]poststarthook/oauth.openshift.io-startoauthclientsbootstrapping ok\n[+]poststarthook/openshift.io-startkubeinformers ok\n[+]poststarthook/start-kube-aggregator-informers ok\n[+]poststarthook/apiservice-registration-controller ok\n[+]poststarthook/apiservice-status-available-controller ok\n[+]poststarthook/apiservice-openapi-controller ok\n[+]poststarthook/kube-apiserver-autoregistration ok\n[-]autoregister-completion failed: reason withheld\nhealthz check failed") has prevented the request from succeeding ()
Error: timed out waiting for the condition解决方法
关闭防火墙，参考https://blog.csdn.net/ytangdigl/article/details/79796961
检查安装后启动的容器
在Pointer中检查启动的容器，如下所示：
openshift启动失败相关推荐
- zabbix4.4 启动失败分析
zabbix是基于WEB界面提供分布式系统监视以及网络监视功能的企业级开源解决方案,能监视各种网络参数,保证服务器系统的安全运营:并提供灵活的通知机制以让系统管理员快速定位/解决存在的各种问题. ...
- Eclipse启动失败：No java virtual machine was found after searching the follwing locations
Eclipse启动失败,错误信息如下如所示: 通过阅读错误信息,可以看到错误原因和 javaw.exe路径 有关: 打开eclipse.ini文件,也就是启动Eclipse的初始化文件: 在本地计算机 ...
- 硬盘满了 mysql启不来_MySQL数据库之磁盘已满造成的mysql启动失败问题分享
本文主要向大家介绍了MySQL数据库之磁盘已满造成的mysql启动失败问题分享 ,通过具体的内容向大家展现,希望对大家学习MySQL数据库有所帮助. 突然发现mysql死活都启不起来了: 复制代码 代 ...
- ArcGis License 启动失败
2019独角兽企业重金招聘Python工程师标准>>> 安装ArcGis10.2后,License启动失败,点击启动没有任何反应,ArcGis License Manager服务显示 ...
- 总结—elasticsearch启动失败的几种情况及解决
1.使用root用户启动失败 在有一次搭建elasticsearch的时候,使用systemctl启动elasticsearch失败,然后在bin目录下面去使用启动脚本启动,发现报错不能用root用户 ...
- sqlnet.ora限制导致双机应用资源启动失败
现场环境: suse9sp3系统下安装oracle9208,为VCS双机.双机配置完成,VCS可以正常启动,刚开始所有资源都可以正常online,但很快server应用资源就会变成offline,从而 ...
- centos 6.0 启动失败提示。
init: prefdm main process -terminated with status 1 init: prefdm respawning too fast,stopped 1.进入单用户 ...
- Android启动失败
今天突然发现ANDROID模拟器启动失败,log显示如下错误信息 ? ERROR: the user data image is used by another emulator. aborting) ...
- mysql启动失败的一个解决方法
mysql启动失败的一个解决方法 参考文章: (1)mysql启动失败的一个解决方法 (2)https://www.cnblogs.com/notfresh/p/mysqlStartError.htm ...
最新文章
- lettuce webdriver 自动化测试---玩转BDD
- 搭建Nginx正向代理
- C#报错：创建调试信息文件 ……obj\Debug\model.pdb: 拒绝访问
- linux系统安装细节及磁盘分区划分
- 为什么MCU也要支持AI功能？
- 高质量c/c++编程(9)
- 支撑性服务 自动化能力
- 80-10-020-原理-Java NIO-HeapByteBuffer
- java linux 信号_Java 中关于信号的处理在Linux下的实现
- 讯飞输入法第11次作答：效率升维、场景细分、个性满足
- java8新特性和汪文君Google Guava实战
- 重磅发布|主机安全联动蜜罐解决方案助力大型攻防演练
- 在教育孩子上少一点功利心，就会快乐？
- 给你的员工一个可期许的未来(by leo)
- 好看的常用背景色RGB数值
- 利用pytorch完成BP神经网络的搭建
- 一键GHOST是什么？
- BZOJ-4811: [Ynoi2017]由乃的OJ (树链剖分 线段树维护区间操作值 好题)
- Ftest（F检验，P值求取）
- 为什么快手不能左右滑了_快手别人直播间右滑进入悬浮窗怎么没用（快手怎么悬浮窗）...