https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
unhealthy how? I usually just look at the service logs in journald, and the static pod logs in /var/log/pods. Everything you need will be in one of those two places.
oh, and the containerd log file too, where that exists
f
I’m currently deploying in an environment with spotty egress, so sometimes when I spin up a new control plane node the etcd connection might timeout (according to the journalctl output), for example, just not sure where to start to debug that
c
by egress, do you mean your connection to the internet?
the rke2-server logs will show timeouts connecting to etcd during initial startup until the etcd static pod starts up. If you have a spotty internet connection, it could be waiting for the etcd image to pull?
Have you tried dropping the airgap image tarballs on the nodes to make sure that all the images are available locally? or using a local registry mirror?
the containerd logs and 
crictl ps
output will show you what’s going on with that, if it is indeed waiting for the etcd image.
f
Thanks for the info, I'll try checking out the containerd and crictl stuff next time.
3 Views
Open in Slack
PreviousNext
Powered by