kubeadm初始化显示kubelet未运行或运行状况良好

时间：2018-08-31 17:07:49

标签： kubernetes kubectl kubeadm

我正在尝试运行Kubernetes，并尝试使用sudo kubeadm init。 根据官方文档的建议，交换已关闭。

问题在于它显示警告：

[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 127.0.0.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 127.0.0.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 127.0.0.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 127.0.0.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 127.0.0.1:10248: connect: connection refused.


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)
            - No internet connection is available so the kubelet cannot pull or find the following control plane images:
                - k8s.gcr.io/kube-apiserver-amd64:v1.11.2
                - k8s.gcr.io/kube-controller-manager-amd64:v1.11.2
                - k8s.gcr.io/kube-scheduler-amd64:v1.11.2
                - k8s.gcr.io/etcd-amd64:3.2.18
                - You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
                  are downloaded locally and cached.

        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'
couldn't initialize a Kubernetes cluster

我正在使用的docker版本是Docker version 17.03.2-ce, build f5ec1e2 我正在使用Ubuntu 16.04 LTS 64bit

泊坞窗图像显示以下图像：

REPOSITORY                                 TAG                 IMAGE ID            CREATED             SIZE
k8s.gcr.io/kube-apiserver-amd64            v1.11.2             821507941e9c        3 weeks ago         187 MB
k8s.gcr.io/kube-controller-manager-amd64   v1.11.2             38521457c799        3 weeks ago         155 MB
k8s.gcr.io/kube-proxy-amd64                v1.11.2             46a3cd725628        3 weeks ago         97.8 MB
k8s.gcr.io/kube-scheduler-amd64            v1.11.2             37a1403e6c1a        3 weeks ago         56.8 MB
k8s.gcr.io/coredns                         1.1.3               b3b94275d97c        3 months ago        45.6 MB
k8s.gcr.io/etcd-amd64                      3.2.18              b8df3b177be2        4 months ago        219 MB
k8s.gcr.io/pause                           3.1                 da86e6ba6ca1        8 months ago        742 kB

完整的日志可以在这里找到： https://pastebin.com/T5V0taE3

我在互联网上找不到任何解决方案。

编辑：

docker ps -a 输出：

ubuntu@ubuntu-HP-Pavilion-15-Notebook-PC:~$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS

journalctl -xeu kubelet 输出：

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.
Sep 01 10:40:05 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: Started kubelet: T
-- 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.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-d
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-d
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: F0901 10:40:06.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: M
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: U
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: F
lines 788-810/810 (END)
-- 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.
Sep 01 10:40:05 ubuntu-HP-Pavilion-15-Notebook-PC 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.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-driver has been deprecated, This parameter should be set via the
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: Flag --cgroup-driver has been deprecated, This parameter should be set via the
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.117131    9107 server.go:408] Version: v1.11.2
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.117406    9107 plugins.go:97] No cloud provider specified.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.121192    9107 certificate_store.go:131] Loading cert/key pair 
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: I0901 10:40:06.145720    9107 server.go:648] --cgroups-per-qos enabled, but --
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC kubelet[9107]: F0901 10:40:06.146074    9107 server.go:262] failed to run Kubelet: Running wi
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Unit entered failed state.
Sep 01 10:40:06 ubuntu-HP-Pavilion-15-Notebook-PC systemd[1]: kubelet.service: Failed with result 'exit-code'.
~


          PORTS               NAMES

任何帮助/建议/评论将不胜感激。

7 个答案:

答案 0 :(得分：2)

该错误已通过

修复。 
sudo swapoff -a
sudo sed -i '/ swap / s/^/#/' /etc/fstab

重新启动计算机。

答案 1 :(得分：1)

使用Kubernetes 1.11.2时，引用CHANGELOG-1.11.md很有用：

  

kubeadm现在检测到Docker cgroup驱动程序并启动kubelet   与匹配的驱动程序。这消除了遇到的常见错误   当Docker cgroup驱动程序与   由于Linux发行版设置不同，一组用于kubelet   Docker的不同cgroup驱动程序，使其难以启动   kubelet正确。

在我看来，您的节点上将一些错误的参数传递给kubelet，而该参数没有启动。

  1. 首先，使用以下命令检查您的码头工人是否有cfgroups：

    docker info | grep -i cgroup

输出应为：

  

Cgroup驱动程序：cgroupfs

  1. 现在在您的节点上查找kubelet服务脚本（可能在/etc/systemd/system/kubelet.service（或类似名称）中，并删除该脚本中与cfgroup有关的所有参数。

  2. 尝试重新启动kubelet服务

  3. 再次检查kubelet的日志（journalctl -xeu kubelet）

答案 2 :(得分：0)

  

sudo sed -i'/ swap / s / ^ /＃/'/ etc / fstab

我花了几天的时间来解决同样的问题，这对我也很有效。 不知道为什么仅使用'sudo swapoff -a'不会有相同的效果。

  

[kubelet-check]似乎kubelet不在运行或运行状况良好。   [kubelet-check]等于'curl -sSL http://localhost:10248/healthz'的HTTP调用失败，并显示错误：Get http://localhost:10248/healthz：拨打tcp 127.0.0.1:10248：connect：连接被拒绝。

这些错误日志确实令人困惑，因为没有线索表明此问题可能与交换配置有关。

答案 3 :(得分：0)

如果您在openstack或任何云上运行，请确保允许安全组中的端口 TCP |入站| 6443 * | Kubernetes API服务器

在我的情况下，这是错误

答案 4 :(得分：0)

即使已被swapoff -a关闭，也不应与swap一起使用。

您应禁用设置文件/etc/fstab

对我来说：

root @ kali：〜＃ cat / etc / fstab 


UUID=ce70d41a-0ce7-42bb-a318-d89369f93b28 / ext4 errors=remount-ro 0 1

#swap was on /dev/sda5 during installation

UUID=2271021b-2aed-4b49-9757-54e7d42ef33e none swap sw 0 0

/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

编辑后：

root @ kali：〜＃ cat / etc / fstab 

UUID=ce70d41a-0ce7-42bb-a318-d89369f93b28 / ext4 errors=remount-ro 0 1

#swap was on /dev/sda5 during installation

#UUID=2271021b-2aed-4b49-9757-54e7d42ef33e none swap sw 0 0

/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

然后.. 重新启动您的计算机

注意：在通过以下方式kubeadm init重启之前，请勿使用reset：

kubeadm reset

答案 5 :(得分：0)

我遇到了完全相同的问题。关闭交换可以解决此问题。 但是我以不同的方式避免了它，因此我将解决方案发布在这里以供参考。

在kubelet中进行交换检查有两个阶段。 一个是kubeadm命令行工具，另一个是kubelet服务。

因此，如果我们不关闭交换功能，则kubeadm应该在下面显示消息

[ERROR Swap]: running with swap on is not supported. Please disable swap

然后它将终止init或join过程。 通过向kubeadm添加参数“ --ignore-preflight-errors = Swap”可以避免kubeadm检查。 这是一个示例：

sudo kubeadm join 10.50.10.198:6443 --token XXXX.XXXXXa     --discovery-token-ca-cert-hash sha256:XX48cb7c381 --ignore-preflight-errors=Swap

但是，如果我们运行此命令。 Kubelet服务将阻止我们，它将发生此线程的问题。 我们可以添加一个配置文件来避免这种情况：

 cd /etc/systemd/system/kubelet.service.d
 touch 20-allow-swap.conf

将这些内容添加到此文件中。

[Service] 
Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false”

然后

 systemctl daemon-reload
 systemctl restart kubelet

最后不要忘了使用“ --ignore-preflight-errors = Swap”来运行kubeadm join agin。

答案 6 :(得分：0)

我最近遇到了类似的问题。问题是 cgroup 驱动程序。 Kubernetes cgroup 驱动程序设置为系统，但 docker 设置为 systemd。所以我创建了'/etc/docker/daemon.json'并在下面添加：

{
"exec-opts": ["native.cgroupdriver=systemd"]
}

然后

 systemctl daemon-reload
 systemctl restart docker
 systemctl restart kubelet

再次运行 kubeadm init 或 kubeadm join。

相关问题
最新问题