[kubelet-check] Initial timeout of 40s passed.

0 votes

Hello,

          I'm getting and error message while installing kubernetes on Ubuntu following the documentation mentioned here https://www.howtoforge.com/how-to-deploy-nginx-on-kubernetes-cluster-on-ubuntu-1804/. The complete error message says as follows:

root@evuser-ThinkPad-T430:/home/evuser/Dockernginx# kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=192.168.31.137[init] Using Kubernetes version: v1.15.2
[preflight] Running pre-flight checks
[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 SystemVerification]: this Docker version is not on the list of validated versions: 19.03.1. Latest validated version: 18.09
[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/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [evuser-thinkpad-t430 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.31.137]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [evuser-thinkpad-t430 localhost] and IPs [192.168.31.137 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [evuser-thinkpad-t430 localhost] and IPs [192.168.31.137 127.0.0.1 ::1]
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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

[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
timed out waiting for the condition

This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
Here is one example how you may list all Kubernetes containers running in docker:
- 'docker ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'docker logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster

After which I did check the kubelet services and it said as mentioned here.

root@evuser-ThinkPad-T430:/home/evuser/Dockernginx# systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2019-08-06 09:18:54 IST; 5min ago
Docs: https://kubernetes.io/docs/home/
Main PID: 24202 (kubelet)
Tasks: 23
Memory: 51.3M
CPU: 9.894s
CGroup: /system.slice/kubelet.service
└─24202 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --c

Aug 06 09:24:27 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:27.726959 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:27 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:27.827159 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:27 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:27.927439 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.027780 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.128013 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.228266 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.328504 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.428718 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.529010 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found
Aug 06 09:24:28 evuser-ThinkPad-T430 kubelet[24202]: E0806 09:24:28.629227 24202 kubelet.go:2248] node "evuser-thinkpad-t430" not found

Now, I'm want to know if I do this "kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=192.168.31.137 --ignore-preflight-errors=

[Courtesy: https://www.edureka.co/community/19089/error-while-doing-kubernetes-init-command].

Aug 6 in Kubernetes by nmentityvibes
• 380 points

edited Aug 6 by Kalgi 1,186 views
Alright, if you are getting issues while creating the dashboard, I am assuming that you have created the cluster and joined your nodes to the cluster.

What error are you getting with the dashboard?

Even I faced a lot of issues the first time I created a Kube cluster.

This is the result of the my kublet pod namespace containers and I'm getting no response while accessing this URL: http://192.168.31.198:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

Here are screenshot images while trying to access it. I've tried installing apache on the kubernetes machine and it worked but I'm not able to access this. Help me with a checklist to access the GUI[graphical user interface].

This message I receive when try to access "192.168.31.198:6443" while trying to join on http and not using "kubeadm join 192.168.31.198:6443 --token gdn12c.i1krjuiaphlaxtwk --discovery-token-ca-cert-hash sha256:6b493c7fea20bb34834f9a1dcf4405130411c70730bf4bf5a0adeb7088966f44". Help me if this is possible or just ignore this one.

Hey @nmentityvibes, can you post the output of kubectl get pods in text format? The image is very blurry to read.

No answer to this question. Be the first to respond.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.

Related Questions In Kubernetes

0 votes
1 answer
0 votes
1 answer

Getting the pod's ip address for the container inside of it

You can make sure that the replication ...READ MORE

answered Aug 24, 2018 in Kubernetes by DareDev
• 6,810 points
131 views
0 votes
2 answers

The Status of nodes shown unknown

This worked for me In Azure, if you ...READ MORE

answered Aug 30, 2018 in Kubernetes by Nilesh
• 6,920 points
924 views
0 votes
1 answer

Unable to get cgroup stats for docker and kubelet services

Try and start kubelet with the following ...READ MORE

answered Sep 3, 2018 in Kubernetes by DareDev
• 6,810 points
349 views
0 votes
1 answer

Spark job using kubernetes instead of yarn

I should be in the format of ...READ MORE

answered Sep 6, 2018 in Kubernetes by Kalgi
• 45,870 points
147 views
0 votes
2 answers

single point of entry for multiple services in kubernetes ingress

I tried having something similar too. Deployment apiVersion: extensions/v1beta1 kind: ...READ MORE

answered Sep 7, 2018 in Kubernetes by Hannah
• 17,070 points
140 views
0 votes
2 answers
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
3,390 views