My rancher stopped working single node docker Is there a way rancher-users #kubernetes

Title

victorious-guitar-37937

11/28/2022, 1:26 PM

My rancher stopped working (single node docker). Is there a way I can further debug this (https://github.com/rancher/rancher/issues/39702). The rancher containers stops after:

[INFO] Waiting for server to become available: Get "<https://127.0.0.1:6443/version?timeout=15m0s>": dial tcp 127.0.0.1:6443: connect: connection refused
exit status 1
2022/11/21 14:41:08 [FATAL] k3s exited with: exit status 1

Does anyone know what is expected at

<https://127.0.0.1:6443>

and how I can debug this ? The kubernetes (formerly created by rancher) is still working.

the kube-api logs are full with

I1128 14:32:48.479587       1 client.go:360] parsed scheme: "passthrough"
I1128 14:32:48.479808       1 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{<https://116.203.221.182:2379>  <nil> 0 <nil>}] <nil> <nil>}
I1128 14:32:48.479843       1 clientconn.go:948] ClientConn switching balancer to "pick_first"

thats the only uncommon thing i could find within the kubernetes cluster

I might have looked completly in the wrong direction, seems to be a cgroup problem

billions-honey-62634

11/29/2022, 4:22 PM

You have to troubleshoot with

docker logs <container id>

Running rancher in single node docker is only recommended for testing. From the docs

A Docker installation of Rancher is recommended only for development and testing purposes. The ability to migrate Rancher to a high-availability cluster depends on the Rancher version:

Install Rancher on top of a HA Kubernetes

kube-api listens on 6443, the docker container spins up a single node k3s "cluster", looks like there is something preventing the container or k3s to start up properly

victorious-guitar-37937

12/01/2022, 10:42 AM

thanks for the help,

docker logs <rancher-id>

only shows that there is no connection. If i inspect the container and got to the mounted

/var/lib/rancher

folder i can see further logs like

k3s.log

that yield further information why k3s does not start. That took me hours to figure out 😞 But atleast I have a new angle for my troubleshooting.

13 Views

#kubernetes Join Slack