couldn't get current server API group list

raziahmed

I have been seeing this message after my server got rebooted. Everything worked perfect before rebooting the server so I am not sure what needs to restarted I checked config file and restarted some of the services but no luck

kubectl get nodes
E0306 20:48:05.554083 230199 memcache.go:265] couldn't get current server API group list: Get "https://192.168.1.228:6443/api?timeout=32s": dial tcp 192.168.1.228:6443: connect: connection refused
E0306 20:48:05.554423 230199 memcache.go:265] couldn't get current server API group list: Get "https://192.168.1.228:6443/api?timeout=32s": dial tcp 192.168.1.228:6443: connect: connection refused
E0306 20:48:05.555716 230199 memcache.go:265] couldn't get current server API group list: Get "https://192.168.1.228:6443/api?timeout=32s": dial tcp 192.168.1.228:6443: connect: connection refused
E0306 20:48:05.556976 230199 memcache.go:265] couldn't get current server API group list: Get "https://192.168.1.228:6443/api?timeout=32s": dial tcp 192.168.1.228:6443: connect: connection refused
E0306 20:48:05.558198 230199 memcache.go:265] couldn't get current server API group list: Get "https://192.168.1.228:6443/api?timeout=32s": dial tcp 192.168.1.228:6443: connect: connection refused
The connection to the server 192.168.1.228:6443 was refused - did you specify the right host or port?

chrispokorni

Hi @raziahmed,

What type of VMs are hosting your cluster? What is the OS installed on these VMs?

Have you checked to see if the container runtime and the kubelet services are active and running?

sudo systemctl status kubelet.service

sudo systemctl status containerd.service

If one of them or both are stopped you can start the one of both and check status again:

sudo systemctl start kubelet.service

sudo systemctl start containerd.service

Regards,
-Chris

fazlur.khan

Try also turning off the swap memory if enabled

swapoff -a