kubeadm join/init error

I am wondering why these errors are occuring in this node but not in my master node even though I followed same documentation for both nodes. Any idea on the following errors?

sudo kubeadm join --token 99cmp6XXXXXXX897f X.X.X.X:XXXX --discovery-token-ca-cert-hash sha256:3a463f0972xxxxxxxxxx42f5bc39bb821995663ac1a045b303e440

[preflight] running pre-flight checks [WARNING RequiredIPVSKernelModulesAvailable]: the IPVS proxier will not be used, because the following required kernel modules are not loaded: [ip_vs ip_vs_rr ip_vs_wrr ip_vs_sh] or no builtin kernel ipvs support: map[ip_vs_sh:{} nf_conntrack_ipv4:{} ip_vs:{} ip_vs_rr:{} ip_vs_wrr:{}]
you can solve this problem with following methods:
 1. Run 'modprobe -- ' to load missing kernel modules;
2. Provide the missing builtin kernel ipvs support

I0813 17:29:42.318378   18250 kernel_validator.go:81] Validating kernel version
I0813 17:29:42.318557   18250 kernel_validator.go:96] Validating kernel config
[discovery] Trying to connect to API Server "X.X.X.X:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://X.X.X.X:6443"
[discovery] Requesting info from "https://X.X.X.X:6443" again to validate TLS against the pinned public key
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "X.X.X.X:6443"
[discovery] Successfully established connection with API Server "X.X.X.X:6443"
[kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.11" ConfigMap in the kube-system namespace
[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[preflight] Activating the kubelet service
[tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "bd-BLR-gpu03" as an annotation
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused.
error uploading crisocket: timed out waiting for the condition

After running this command I got bit more info:

sudo journalctl -xeu kubelet
-- Subject: Unit kubelet.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kubelet.service has finished shutting down.
Aug 13 17:34:04 BD-BLR systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kubelet.service has finished starting up.
--
-- The start-up result is done.
Aug 13 17:34:05 BD-BLR kubelet[25954]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --con
Aug 13 17:34:05 BD-BLR kubelet[25954]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --con
Aug 13 17:34:05 BD-BLR kubelet[25954]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --con
Aug 13 17:34:05 BD-BLR kubelet[25954]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --con
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.054375   25954 server.go:408] Version: v1.11.2
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.054597   25954 plugins.go:97] No cloud provider specified.
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.078725   25954 certificate_store.go:131] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-cur
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188090   25954 server.go:648] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188576   25954 container_manager_linux.go:243] container manager verified user specified cgroup-root exists:
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188613   25954 container_manager_linux.go:248] Creating Container Manager object based on Node Config: {Runt
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188855   25954 container_manager_linux.go:267] Creating device plugin manager: true
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188893   25954 state_mem.go:36] [cpumanager] initializing new in-memory state store
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188963   25954 state_mem.go:84] [cpumanager] updated default cpuset: ""
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.188980   25954 state_mem.go:92] [cpumanager] updated cpuset assignments: "map[]"
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.189168   25954 kubelet.go:274] Adding pod path: /etc/kubernetes/manifests
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.189209   25954 kubelet.go:299] Watching apiserver
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.192752   25954 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.192786   25954 client.go:104] Start docker client with request timeout=2m0s
Aug 13 17:34:05 BD-BLR kubelet[25954]: W0813 17:34:05.194140   25954 docker_service.go:545] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, f
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.194170   25954 docker_service.go:238] Hairpin mode set to "hairpin-veth"
Aug 13 17:34:05 BD-BLR kubelet[25954]: W0813 17:34:05.194279   25954 cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d
Aug 13 17:34:05 BD-BLR kubelet[25954]: W0813 17:34:05.196496   25954 hostport_manager.go:68] The binary conntrack is not installed, this can cause failures in net
Aug 13 17:34:05 BD-BLR kubelet[25954]: W0813 17:34:05.196565   25954 cni.go:172] Unable to update cni config: No networks found in /etc/cni/net.d
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.196591   25954 docker_service.go:253] Docker cri networking managed by cni
Aug 13 17:34:05 BD-BLR kubelet[25954]: I0813 17:34:05.241205   25954 docker_service.go:258] Docker Info: &{ID:YELA:DBWD:4E7W:WG26:DC5Y:2SAH:SWPE:PB5A:SUYO:GPKY:CZ
Aug 13 17:34:05 BD-BLR kubelet[25954]: F0813 17:34:05.241460   25954 server.go:262] failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgr
Aug 13 17:34:05 BD-BLR systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Aug 13 17:34:05 BD-BLR systemd[1]: kubelet.service: Unit entered failed state.
Aug 13 17:34:05 BD-BLR systemd[1]: kubelet.service: Failed with result 'exit-code'.

Kindly direct me to resolve the errors.

kubeadm join/init error

Pavan Kumar

Lubomir I. Ivanov

Pavan Kumar

Pavan Kumar

Lubomir I. Ivanov