· 6 years ago · Oct 25, 2019, 10:02 AM
1admin@ip-172-21-59-251:~$ kubeadm version
2kubeadm version: &version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:15:39Z", GoVersion:"go1. 12.10", Compiler:"gc", Platform:"linux/amd64"}
3admin@ip-172-21-59-251:~$ sudo kubeadm init --apiserver-advertise-address=172.21.59.251
4[init] Using Kubernetes version: v1.16.2
5[preflight] Running pre-flight checks
6 [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/
7error execution phase preflight: [preflight] Some fatal errors occurred:
8 [ERROR Port-10251]: Port 10251 is in use
9 [ERROR Port-10252]: Port 10252 is in use
10 [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
11 [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
12 [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
13 [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
14 [ERROR KubeletVersion]: Kubelet version "1.7.10" is lower than kubeadm can support. Please upgrade kubelet
15 [ERROR Port-10250]: Port 10250 is in use
16 [ERROR Port-2380]: Port 2380 is in use
17[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
18To see the stack trace of this error execute with --v=5 or higher
19admin@ip-172-21-59-251:~$ kubectl get nodes
20The connection to the server 127.0.0.1 was refused - did you specify the right host or port?
21admin@ip-172-21-59-251:~$ sudo kubeadm init --apiserver-advertise-address=172.21.59.251 --ignore-preflight-errors=all
22[init] Using Kubernetes version: v1.16.2
23[preflight] Running pre-flight checks
24 [WARNING Port-10251]: Port 10251 is in use
25 [WARNING Port-10252]: Port 10252 is in use
26 [WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
27 [WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
28 [WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
29 [WARNING FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
30 [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/
31 [WARNING KubeletVersion]: Kubelet version "1.7.10" is lower than kubeadm can support. Please upgrade kubelet
32 [WARNING Port-10250]: Port 10250 is in use
33 [WARNING Port-2380]: Port 2380 is in use
34[preflight] Pulling images required for setting up a Kubernetes cluster
35[preflight] This might take a minute or two, depending on the speed of your internet connection
36[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
37[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
38[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
39[kubelet-start] Activating the kubelet service
40[certs] Using certificateDir folder "/etc/kubernetes/pki"
41[certs] Using existing ca certificate authority
42[certs] Using existing apiserver certificate and key on disk
43[certs] Using existing apiserver-kubelet-client certificate and key on disk
44[certs] Using existing front-proxy-ca certificate authority
45[certs] Using existing front-proxy-client certificate and key on disk
46[certs] Using existing etcd/ca certificate authority
47[certs] Using existing etcd/server certificate and key on disk
48[certs] Using existing etcd/peer certificate and key on disk
49[certs] Using existing etcd/healthcheck-client certificate and key on disk
50[certs] Using existing apiserver-etcd-client certificate and key on disk
51[certs] Using the existing "sa" key
52[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
53[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/admin.conf"
54[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/kubelet.conf"
55[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/controller-manager.conf"
56[kubeconfig] Using existing kubeconfig file: "/etc/kubernetes/scheduler.conf"
57[control-plane] Using manifest folder "/etc/kubernetes/manifests"
58[control-plane] Creating static Pod manifest for "kube-apiserver"
59[control-plane] Creating static Pod manifest for "kube-controller-manager"
60[control-plane] Creating static Pod manifest for "kube-scheduler"
61[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
62[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 4m0s
63[kubelet-check] Initial timeout of 40s passed.
64
65Unfortunately, an error has occurred:
66 timed out waiting for the condition
67
68This error is likely caused by:
69 - The kubelet is not running
70 - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
71
72If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
73 - 'systemctl status kubelet'
74 - 'journalctl -xeu kubelet'
75
76Additionally, a control plane component may have crashed or exited when started by the container runtime.
77To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
78Here is one example how you may list all Kubernetes containers running in docker:
79 - 'docker ps -a | grep kube | grep -v pause'
80 Once you have found the failing container, you can inspect its logs with:
81 - 'docker logs CONTAINERID'
82error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
83To see the stack trace of this error execute with --v=5 or higher
84admin@ip-172-21-59-251:~$ systemctl status kubelet
85Failed to get D-Bus connection: No such file or directory
86admin@ip-172-21-59-251:~$ systemctl status kubelet.service
87Failed to get D-Bus connection: No such file or directory
88admin@ip-172-21-59-251:~$ sudo systemctl status kubelet.service
89● kubelet.service - Kubernetes Kubelet Server
90 Loaded: loaded (/lib/systemd/system/kubelet.service; static)
91 Drop-In: /etc/systemd/system/kubelet.service.d
92 └─10-kubeadm.conf
93 Active: active (running) since Fri 2019-10-25 09:52:13 UTC; 5min ago
94 Docs: https://github.com/kubernetes/kubernetes
95 Main PID: 9554 (kubelet)
96 CGroup: /system.slice/kubelet.service
97 └─9554 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgrou...
98
99Oct 25 09:57:16 ip-172-21-59-251 kubelet[9554]: E1025 09:57:16.910172 9554 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:459: Failed to list *v1.Node: Get https://172.21...ction refused
100Oct 25 09:57:16 ip-172-21-59-251 kubelet[9554]: E1025 09:57:16.993091 9554 kubelet.go:2267] node "ip-172-21-59-251" not found
101Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.093280 9554 kubelet.go:2267] node "ip-172-21-59-251" not found
102Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.110190 9554 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:450: Failed to list *v1.Service: Get https://172...ction refused
103Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.193452 9554 kubelet.go:2267] node "ip-172-21-59-251" not found
104Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: I1025 09:57:17.210495 9554 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
105Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: I1025 09:57:17.212488 9554 kubelet_node_status.go:72] Attempting to register node ip-172-21-59-251
106Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.293627 9554 kubelet.go:2267] node "ip-172-21-59-251" not found
107Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.310166 9554 kubelet_node_status.go:94] Unable to register node "ip-172-21-59-251" with API server: Post https://172.21....ction refused
108Oct 25 09:57:17 ip-172-21-59-251 kubelet[9554]: E1025 09:57:17.393812 9554 kubelet.go:2267] node "ip-172-21-59-251" not found
109Hint: Some lines were ellipsized, use -l to show in full.