Docker IBM云专用端口8443在重新启动后未侦听
您是否检查过在执行重新启动后是否有一条防火墙规则消失了?Docker IBM云专用端口8443在重新启动后未侦听,docker,ibm-cloud,ibm-cloud-private,Docker,Ibm Cloud,Ibm Cloud Private,您是否检查过在执行重新启动后是否有一条防火墙规则消失了? 我们在重新启动ICP时会遇到与群集启动相关的问题。控制台抛出500个内部服务器错误。每次我面对这个问题,我都会尝试下面的解决方案。 1. : 点击这个链接 2.如果问题没有得到解决,请验证 systemctl状态kubelet docker 3.执行上述两种解决方案后,请等待几分钟,清除浏览器缓存,然后打开控制台。很多时候,即使解决方案由于缓存问题已修复,控制台也不会打开 所有容器也正常运行,仍然无法打开ConsoleAnks现在it工
我们在重新启动ICP时会遇到与群集启动相关的问题。控制台抛出500个内部服务器错误。每次我面对这个问题,我都会尝试下面的解决方案。 1. : 点击这个链接 2.如果问题没有得到解决,请验证 systemctl状态kubelet docker
3.执行上述两种解决方案后,请等待几分钟,清除浏览器缓存,然后打开控制台。很多时候,即使解决方案由于缓存问题已修复,控制台也不会打开 所有容器也正常运行,仍然无法打开ConsoleAnks现在it工作我甚至已禁用防火墙仍然无法连接到端口8443 OK然后-确保您使用了正确的步骤重新启动群集:ICO是什么版本?我使用的是icp ce版本2.1.0.2。我还会再次检查重启步骤。
root@pact1:~# kubectl -s http://localhost:8888 get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system auth-apikeys-9bx2r 1/1 Running 3 4d
kube-system auth-idp-kkt6m 3/3 Running 9 4d
kube-system auth-pap-6brhh 1/1 Running 3 4d
kube-system auth-pdp-6ztzn 1/1 Running 3 4d
kube-system calico-kube-controllers-68786dd655-xrcs4 1/1 Running 4 5d
kube-system calico-node-amd64-48t8h 2/2 Running 8 5d
kube-system catalog-catalog-apiserver-hj6pt 1/1 Running 6 4d
kube-system catalog-catalog-controller-manager-59d9b88c9d-qgd9z 1/1 Running 8 4d
kube-system catalog-ui-42vlk 1/1 Running 4 4d
kube-system default-http-backend-6858c684cd-n222g 1/1 Running 5 4d
kube-system elasticsearch-client-56cf688d8f-l74tf 2/2 Running 8 4d
kube-system elasticsearch-data-0 1/1 Running 4 4d
kube-system elasticsearch-master-86fddbdcb-8bl7p 1/1 Running 4 4d
kube-system filebeat-ds-amd64-hbvrw 1/1 Running 4 4d
kube-system heapster-96c84478b-27spb 2/2 Running 9 4d
kube-system helm-api-7767fbc785-kng26 2/2 Running 8 4d
kube-system helmrepo-86c469554-4nlkf 1/1 Running 4 4d
kube-system icp-ds-0 1/1 Running 4 4d
kube-system icp-management-ingress-lkjlm 1/1 Running 4 4d
kube-system image-manager-0 2/2 Running 8 4d
kube-system k8s-etcd-9.199.144.168 1/1 Running 4 5d
kube-system k8s-mariadb-9.199.144.168 1/1 Running 5 4d
kube-system k8s-master-9.199.144.168 3/3 Running 12 5d
kube-system k8s-proxy-9.199.144.168 1/1 Running 4 5d
kube-system kube-dns-amd64-x9vb6 3/3 Running 12 4d
kube-system logstash-5c8c4954d9-bcfkz 1/1 Running 4 4d
kube-system metering-dm-5c4f8bf7c7-jp6xz 1/1 Running 4 4d
kube-system metering-reader-amd64-75rv2 1/1 Running 4 4d
kube-system metering-server-55c4d77f4c-86l4x 1/1 Running 4 4d
kube-system metering-ui-59c65d97d6-mbw45 1/1 Running 4 4d
kube-system monitoring-exporter-d8568ffff-sxvtq 1/1 Running 4 4d
kube-system monitoring-grafana-78dd9bd7c9-d9hrr 2/2 Running 8 4d
kube-system monitoring-prometheus-7994986858-z2lsm 3/3 Running 12 4d
kube-system monitoring-prometheus-alertmanager-7dc884c44d-4wbf8 3/3 Running 12 4d
kube-system monitoring-prometheus-kubestatemetrics-798dd85965-pwxth 1/1 Running 4 4d
kube-system monitoring-prometheus-nodeexporter-amd64-tzndd 1/1 Running 4 4d
kube-system nginx-ingress-lb-amd64-546w7 1/1 Running 7 4d
kube-system platform-api-gn4gf 1/1 Running 4 4d
kube-system platform-deploy-f6dhv 1/1 Running 4 4d
kube-system platform-ui-cr9n7 1/1 Running 4 4d
kube-system rescheduler-vlfd2 1/1 Running 4 4d
kube-system tiller-deploy-69f658499-6vwpl 1/1 Running 4 4d
kube-system unified-router-4qz2r 1/1 Running 4 4d