Troubleshooting Worker Nodes and Generic Components

This section applies to every node as it includes components that run on nodes with any role.

Check if the Containers are Running

There are two specific containers launched on nodes with the worker role:

  • kubelet
  • kube-proxy

The containers should have status Up. The duration shown after Up is the time the container has been running.

  1. docker ps -a -f=name='kubelet|kube-proxy'

Example output:

  1. CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS              PORTS               NAMES
  2. 158d0dcc33a5        rancher/hyperkube:v1.11.5-rancher1   "/opt/rke-tools/en..."   3 hours ago         Up 3 hours                              kube-proxy
  3. a30717ecfb55        rancher/hyperkube:v1.11.5-rancher1   "/opt/rke-tools/en..."   3 hours ago         Up 3 hours                              kubelet

Container Logging

The logging of the containers can contain information on what the problem could be.

  1. docker logs kubelet
  2. docker logs kube-proxy