title: kubelet.service: Main process exited, code=exited, status=255/n/a
body: <p>I am making test Cluster following this instructions:
  <a href="https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/" rel="noreferrer">https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/</a>
  and </p>
  
  <p><a href="https://kubernetes.io/docs/getting-started-guides/fedora/flannel_multi_node_cluster/" rel="noreferrer">https://kubernetes.io/docs/getting-started-guides/fedora/flannel_multi_node_cluster/</a>
  unfortunately when I check my nodes following occurs:</p>
  
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>kubectl get no
  NAME                        STATUS     ROLES     AGE       VERSION
  pccshost2.lan.proficom.de   NotReady   &lt;none&gt;    19h       v1.10.3
  pccshost3.lan.proficom.de   NotReady   &lt;none&gt;    19h       v1.10.3</code></pre>
  </div>
  </div>
  </p>
  
  <p>so far as I get this problem is connected with not working kubelet.service on master-node:</p>
  
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>systemctl status kubelet.service
  
  kubelet.service - Kubernetes Kubelet Server
     Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Wed 2019-03-06 10:38:30 CET; 32min ago
       Docs: https://github.com/GoogleCloudPlatform/kubernetes
    Process: 14057 ExecStart=/usr/bin/kubelet $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBELET_API_SERVER $KUBELET_ADDRESS $KUBELET_PORT $KUBELET_HOSTNAME $KUBE_ALLOW_PRIV $KU&gt;
   Main PID: 14057 (code=exited, status=255)
        CPU: 271ms
  
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Failed with result 'exit-code'.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Consumed 271ms CPU time
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Service RestartSec=100ms expired, scheduling restart.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 5.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: Stopped Kubernetes Kubelet Server.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Consumed 271ms CPU time
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Start request repeated too quickly.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: kubelet.service: Failed with result 'exit-code'.
  Mar 06 10:38:30 pccshost1.lan.proficom.de systemd[1]: Failed to start Kubernetes Kubelet Server.</code></pre>
  </div>
  </div>
  </p>
  
  <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
  <div class="snippet-code">
  <pre class="snippet-code-html lang-html prettyprint-override"><code>~kubectl describe node
  
   Normal  Starting                 9s    kubelet, pccshost2.lan.proficom.de  Starting kubelet.
    Normal  NodeHasSufficientDisk    9s    kubelet, pccshost2.lan.proficom.de  Node pccshost2.lan.proficom.de status is now: NodeHasSufficientDisk
    Normal  NodeHasSufficientMemory  9s    kubelet, pccshost2.lan.proficom.de  Node pccshost2.lan.proficom.de status is now: NodeHasSufficientMemory
    Normal  NodeHasNoDiskPressure    9s    kubelet, pccshost2.lan.proficom.de  Node pccshost2.lan.proficom.de status is now: NodeHasNoDiskPressure
    Normal  NodeHasSufficientPID     9s    kubelet, pccshost2.lan.proficom.de  Node pccshost2.lan.proficom.de status is now: NodeHasSufficientPID</code></pre>
  </div>
  </div>
  </p>
  
  <p>can somebody give an advice what is happening here and how can I fix it? Thx</p>