rancher-docs/archived_docs/en/version-2.5/troubleshooting/kubernetes-components/troubleshooting-worker-nodes-and-generic-components.md at 8c8f8a5f2edec3d7f5abc321e7ca42e681919fdb

mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-05 20:53:33 +00:00

Files

T

Lucas Saintarbor 8c76072fd2 Archive v2.5 docs (#1634 )

* Update docusaurus.config.js/Remove v2.5 redirects and update v2.5 label and path

* Update version-2.5-sidebars.json with notice

* Remove v2.5 files/Add v2.5 files to archived_docs folder

* Fix broken link

* Fix broken link/typo

* Fix broken links

2025-02-18 14:08:09 -08:00

1.3 KiB

Raw Blame History

title

title
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.

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

Example output:

CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS              PORTS               NAMES
158d0dcc33a5        rancher/hyperkube:v1.11.5-rancher1   "/opt/rke-tools/en..."   3 hours ago         Up 3 hours                              kube-proxy
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.

docker logs kubelet
docker logs kube-proxy

1.3 KiB Raw Blame History

Check if the Containers are Running

Container Logging

1.3 KiB

Raw Blame History