kubelet n'a pas réussi à démarrer-Active: échoué (résultat: limite de démarrage)

problème

kubelet n'a pas pu démarrer - Actif: échec (résultat: limite de démarrage).

# systemctl status kubelet

● kubelet.service - Kubernetes Kubelet Server
   Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Sat 2018-07-14 11:41:02 CST; 3min 55s ago
     Docs: https://github.com/kubernetes/kubernetes
  Process: 5360 ExecStart=/usr/local/kubernetes/bin/kubelet $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBELET_CONFIG $KUBELET_HOSTNAME $KUBELET_POD_INFRA_CONTAINER $KUBELET_ARGS (code=exited, status=255)
 Main PID: 5360 (code=exited, status=255)

Jul 14 11:41:02 docker-hub systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Jul 14 11:41:02 docker-hub systemd[1]: Unit kubelet.service entered failed state.
Jul 14 11:41:02 docker-hub systemd[1]: kubelet.service failed.
Jul 14 11:41:02 docker-hub systemd[1]: kubelet.service holdoff time over, scheduling restart.
Jul 14 11:41:02 docker-hub systemd[1]: start request repeated too quickly for kubelet.service
Jul 14 11:41:02 docker-hub systemd[1]: Failed to start Kubernetes Kubelet Server.
Jul 14 11:41:02 docker-hub systemd[1]: Unit kubelet.service entered failed state.
Jul 14 11:41:02 docker-hub systemd[1]: kubelet.service failed.

Solution

Désactivez la mémoire d'échange.

# swapoff -a

Je suppose que tu aimes

Origine blog.csdn.net/yjk13703623757/article/details/108105751
conseillé
Classement