This message was deleted.
# rke2
a
This message was deleted.
a
Rancher version is 2.7.5
c
Have you looked at anything beyond the provisioning logs? like, logging in to the node and checking pod status, rke2 service log, and so on?
provisioning log isn’t going to tell you much more than “its not working”
a
I logged into the node. I am not sure of the location of kubectl because when I tried it said it needs to install kubectl
root@scale01-pool1-5a9fd594-nj9tb:~# /var/lib/rancher/rke2/bin/kubectl get pods -A E0929 021749.041917 12670 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [:1]8080: connect: connection refused E0929 021749.042439 12670 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [:1]8080: connect: connection refused E0929 021749.044193 12670 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [:1]8080: connect: connection refused E0929 021749.045806 12670 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [:1]8080: connect: connection refused E0929 021749.047526 12670 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [:1]8080: connect: connection refused The connection to the server localhost:8080 was refused - did you specify the right host or port? root@scale01-pool1-5a9fd594-nj9tb:~#
c
You don’t need to use kubectl 1. check the rke2-server journald logs 2. check /var/log/pods 3. use
CONTAINER_RUNTIME_ENDPOINT="unix:///var/run/k3s/containerd/containerd.sock crictl ps -a
to check running containers