wcsemail 我也是遇到各种奇怪的问题

fatal: [ks-allinone]: FAILED! => {
“attempts”: 30,
“changed”: true,
“cmd”: “/usr/local/bin/kubectl get pod -n kubesphere-system | grep Running | grep ks-installer”,
“delta”: “0:00:00.085104″,
“end”: “2020-05-16 14:13:58.346256″,
“rc”: 1,
“start”: “2020-05-16 14:13:58.261152”
}

MSG:

non-zero return code

PLAY RECAP *************************************************************************************************************
ks-allinone : ok=135 changed=15 unreachable=0 failed=1
遇到各种问题，反复卸载安装，结果还不一样

Feynman 那就是了，在研究这个能不能在线安装使用本地局域网的harbor做加速，所以遇到了这个问题了

centos7.3操作系统可以嘛

Feynman 离线只能安装单master吗?

Feynman

### ### 安装成功了，但是linux系统重启，30880端口没启动起来

[root@ks-allinone _]# kubectl get pods -n kube-system
Unable to connect to the server: net/http: TLS handshake timeout
[root@ks-allinone _]# kubectl get pods -n kube-system
The connection to the server 192.168.3.177:6443 was refused - did you specify the right host or port?
[root@ks-allinone _]# kubectl get pods -n kube-system
The connection to the server 192.168.3.177:6443 was refused - did you specify the right host or port?
[root@ks-allinone _]# kubectl get pods -n kube-system
The connection to the server 192.168.3.177:6443 was refused - did you specify the right host or port?

Feynman docker### 有起来，现在初步怀疑跟linux ###操作系统时间有关系
安装 好的时间是5月24日20点（实际时间是9：00），我把linux### 时间一调整，重启系统，30880端口就没起来

请问这是什么原因？

SOVLOOKUP

SOVLOOKUP tiller情况

安装成功，我的环境连接SSH有点问题，改成了免密登录解决。

安装一直出现如下错误，还不停的重试，请问怎么解决

received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json818424021: no space left on device
192.168.28.150:5000/k8scsi/csi-attacher:v2.0.0
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json314613296: no space left on device
The push refers to repository [192.168.28.150:5000/k8scsi/csi-attacher]
94f49fb5c15d: Retrying in 1 second
932da5156413: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json316807511: no space left on device
192.168.28.150:5000/k8scsi/csi-node-driver-registrar:v1.2.0
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json160083146: no space left on device
The push refers to repository [192.168.28.150:5000/k8scsi/csi-node-driver-registrar]
e242ebe3c0e7: Retrying in 1 second
932da5156413: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json073381225: no space left on device
192.168.28.150:5000/kubesphere/cloud-controller-manager:v1.4.0
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json696550324: no space left on device
The push refers to repository [192.168.28.150:5000/kubesphere/cloud-controller-manager]
7371592b8bed: Retrying in 1 second
68b0cbfdd0ed: Retrying in 1 second
73046094a9b8: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json020405123: no space left on device
192.168.28.150:5000/google-containers/k8s-dns-node-cache:1.15.5
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json249889030: no space left on device
The push refers to repository [192.168.28.150:5000/google-containers/k8s-dns-node-cache]
5d024027846e: Retrying in 1 second
a95807b0aa21: Retrying in 1 second
fe9a8b4f1dcc: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json278284461: no space left on device
192.168.28.150:5000/library/redis:5.0.5-alpine
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json442011176: no space left on device
The push refers to repository [192.168.28.150:5000/library/redis]
76ff8be8279a: Retrying in 1 second
9559709fdf7f: Retrying in 1 second
b499b26b07f7: Retrying in 1 second
1ac7839ac772: Retrying in 1 second
b34cd2e3555a: Retrying in 1 second
03901b4a2ea8: Waiting
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json718429543: no space left on device
192.168.28.150:5000/kubesphere/configmap-reload:v0.3.0
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json499708314: no space left on device
The push refers to repository [192.168.28.150:5000/kubesphere/configmap-reload]
f78d3758f4e1: Retrying in 1 second
0d315111b484: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json578320433: no space left on device
192.168.28.150:5000/library/haproxy:2.0.4
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json021125596: no space left on device
The push refers to repository [192.168.28.150:5000/library/haproxy]
ceb43b25ba94: Retrying in 1 second
f7e0348535e3: Retrying in 1 second
1c95c77433e8: Retrying in 1 second
received unexpected HTTP status: 500 Internal Server Error
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json199333771: no space left on device
192.168.28.150:5000/minio/mc:RELEASE.2019-08-07T23-14-43Z
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json619561326: no space left on device
The push refers to repository [192.168.28.150:5000/minio/mc]

zhoachenIt “no space left on device” 这么明显的提示，没空间了，需要清理一下，可以用docker
system prune的方式，查查具体命令以及每个命令的后果是什么再处理

这个你看了吗？https://kubesphere.com.cn/forum/d/852-kubesphere-2-1-1-kubernetes

rayzhou2017 谢谢果然是磁盘满了 我现在扩容到200G了在看看可以不

您好，麻烦请教下如果kubesphere安装好之后，能否把 Docker Local Registry卸载掉，更换成harbor具体操作得怎么做？谢谢

离线安装，最小化安装提示成功后，查看ks-apigateway的pod没正常启动

有遇到这样的问题吗？

这个怎么处理

30880端口做负载后，浏览器访问虚拟后的IP地址打开提示：client send an http request to https server
访问真实的IP地址正常，请问是哪里有问题？

找到原因了 是 common.yaml nfsserver 相关 未配置

我从2.2.0升级到2.2.1出现如下错误，我是用离线包来升级的
FAILED - RETRYING: download_container | Download image if required ( 10.1.1.78:5000/google-containers/hyperkube:v1.16.7 ) (1 retries left).
fatal: [node3 -> master1]: FAILED! => {
“attempts”: 4,
“changed”: true,
“cmd”: [
“/usr/bin/docker”,
“pull”,
“10.1.1.78:5000/google-containers/hyperkube:v1.16.7”
],
“delta”: “0:00:00.062649″,
“end”: “2020-07-24 16:09:46.198996”,
“rc”: 1,
“start”: “2020-07-24 16:09:46.136347”
}

STDERR:

Error response from daemon: manifest for 10.1.1.78:5000/google-containers/hyperkube:v1.16.7 not found

基础环境需要哪些，ansible，docker？ 望在文档中标识一下

请问一下安装了一个多小时提示这个报错是哪里配置错了？新机器，环境干净，前面uninstall过两次

FAILED - RETRYING: kubeadm | Initialize first master (3 retries left).
FAILED - RETRYING: kubeadm | Initialize first master (2 retries left).
FAILED - RETRYING: kubeadm | Initialize first master (1 retries left).
fatal: [master1]: FAILED! => {
“attempts”: 3,
“changed”: true,
“cmd”: [
“timeout”,
“-k”,
“300s”,
“300s”,
“/usr/local/bin/kubeadm”,
“init”,
“–config=/etc/kubernetes/kubeadm-config.yaml”,
“–ignore-preflight-errors=all”,
“–skip-phases=addon/coredns”,
“–upload-certs”
],
“delta”: “0:05:00.037168″,
“end”: “2020-08-07 14:50:01.396185”,
“failed_when_result”: true,
“rc”: 124,
“start”: “2020-08-07 14:45:01.359017”
}

STDOUT:

[init] Using Kubernetes version: v1.16.7
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using ‘kubeadm config images pull’
[kubelet-start] Writing kubelet environment file with flags to file “/var/lib/kubelet/kubeadm-flags.env”
[kubelet-start] Writing kubelet configuration to file “/var/lib/kubelet/config.yaml”
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder “/etc/kubernetes/ssl”
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Using existing apiserver-kubelet-client certificate and key on disk
[certs] Using existing front-proxy-ca certificate authority
[certs] Using existing front-proxy-client certificate and key on disk
[certs] External etcd mode: Skipping etcd/ca certificate authority generation
[certs] External etcd mode: Skipping etcd/server certificate generation
[certs] External etcd mode: Skipping etcd/peer certificate generation
[certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation
[certs] External etcd mode: Skipping apiserver-etcd-client certificate generation
[certs] Using the existing “sa” key
[kubeconfig] Using kubeconfig folder “/etc/kubernetes”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/admin.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/kubelet.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/controller-manager.conf”
[kubeconfig] Using existing kubeconfig file: “/etc/kubernetes/scheduler.conf”
[control-plane] Using manifest folder “/etc/kubernetes/manifests”
[control-plane] Creating static Pod manifest for “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-controller-manager”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[control-plane] Creating static Pod manifest for “kube-scheduler”
[controlplane] Adding extra host path mount “etc-pki-tls” to “kube-apiserver”
[controlplane] Adding extra host path mount “etc-pki-ca-trust” to “kube-apiserver”
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory “/etc/kubernetes/manifests”. This can take up to 5m0s
[kubelet-check] Initial timeout of 40s passed.

STDERR:

[WARNING Port-6443]: Port 6443 is in use
[WARNING Port-10251]: Port 10251 is in use
[WARNING Port-10252]: Port 10252 is in use
[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[WARNING Port-10250]: Port 10250 is in use

MSG:

non-zero return code

NO MORE HOSTS LEFT *******************************************************************************************************

PLAY RECAP ***************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=0

master1 : ok=417 changed=76 unreachable=0 failed=1

master2 : ok=406 changed=78 unreachable=0 failed=0

master3 : ok=406 changed=78 unreachable=0 failed=0

node1 : ok=330 changed=61 unreachable=0 failed=0

Friday 07 August 2020 14:50:01 +0800 (0:20:16.326) 0:30:25.065 *********

kubernetes/master : kubeadm | Initialize first master ———————————————————- 1216.33s
container-engine/docker : ensure docker packages are installed ————————————————— 36.87s
kubernetes/preinstall : Install packages requirements ———————————————————— 26.10s
etcd : Gen_certs | Write etcd master certs ———————————————————————– 23.58s
container-engine/docker : Docker | reload docker —————————————————————– 15.88s
bootstrap-os : Install libselinux python package —————————————————————— 8.91s
etcd : Gen_certs | Gather etcd master certs ———————————————————————– 6.01s
etcd : Configure | Check if etcd cluster is healthy ————————————————————— 4.87s
etcd : Install | Copy etcdctl binary from docker container ——————————————————– 4.78s
download : download | Download files / images ——————————————————————— 4.45s
download : download_file | Download item ————————————————————————– 4.26s
download : download_file | Download item ————————————————————————– 4.09s
etcd : wait for etcd up ——————————————————————————————- 3.50s
etcd : reload etcd ———————————————————————————————— 3.20s
kubernetes/node : install | Copy kubelet binary from download dir ————————————————- 3.13s
download : download | Sync files / images from ansible host to nodes ———————————————- 3.08s
etcd : Gen_certs | run cert generation script ——————————————————————— 2.77s
download : download_file | Download item ————————————————————————– 2.62s
chrony : start chrony server ————————————————————————————– 2.47s
container-engine/docker : ensure service is started if docker packages are already present ———————— 2.45s
failed!

please refer to https://kubesphere.io/docs/v2.1/zh-CN/faq/faq-install/

TASK [kubernetes/master : kubeadm | Initialize first master] *************************************************************
Friday 07 August 2020 15:18:06 +0800 (0:00:00.461) 0:08:36.763 *********
skipping: [master2]
skipping: [master3]
就是在初始化master1的时候报的错

离线安装报这个错误，麻烦帮忙看下什么问题？

DukeChiang 请问这个问题解决了吗？我也遇到这个问题了，报的同样的错

fnag_huna
看样子是pip源的问题
如果没有用glusterfs的话，可以在kubesphere/roles/prepare/nodes/tasks/main.yaml中注释掉glusterfs相关的任务。

v3.0.0已发布，可以试试

Cauchy 感谢回复！但尝试注释以后得到了同样的结果。
umount: /kubeinstaller/yum_repo/iso: mountpoint not found这行提示是否提示我未将镜像文件放到yum_repo中呢？

fnag_huna

这个只是说明umount的时候没有对应的挂载点。
还是那个pip | Installing pip报错吗？注释掉的话应该就不会执行那个task了呀。

Cauchy 我没有找到您说的这一行在哪里，我的报错信息一直是这样的