Error while doing kubernetes-init command

Question

I'm trying to run the following command

sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=192.168.56.56 --ignore-preflight-errors=...

I get the following errors

[init] using Kubernetes version: v1.11.2
[preflight] running pre-flight checks
I0905 15:35:34.143850   32381 kernel_validator.go:81] Validating kernel version
I0905 15:35:34.144318   32381 kernel_validator.go:96] Validating kernel config
[preflight] Some fatal errors occurred:
 [ERROR Port-6443]: Port 6443 is in use
 [ERROR Port-10251]: Port 10251 is in use
[ERROR Port-10252]: Port 10252 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 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=...`

Whats the issue?

Answer 1

The reason that it mentions the port is in use is because you already ran kubeadm init once and it has already changed a number of things.

run kubeadm reset first to undo all of the changes from the first time you ran it.

Then run systemctl restart kubelet

Finally, when you run kubeadm init you should no longer get the error.

If you are interested in knowing more about Kubernetes, then consider taking  CKA Certification Course.

Comments

Issue not solved by above steps

kubeadm reset

systemctl restart kubelet

Answer 2

Run docker ps -a | grep kube to find related container logs, such as apiserver. 

Answer 3

Run kubeadm reset to revert any changes made to this host by kubeadm init. And try setting up the cluster again! This helped me :)

Comments

Hey thanks! That worked for me.

But now I have another error

The connection to the server x.x.x.x:8080 was refused - did you specify the right host or port?

when I do kubectl apply -f https://git.io/weave-kube

---

Have a look at this thread:

https://www.edureka.co/community/18633/error-saying-connection-server-localhost-refused-specify?