Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error Unable to connect to the server ... after reboot.

See original GitHub issue

I create microk8s and node1.

windows 10 hyper-v

I use powershell ,my step :

microk8s install
microk8s config > ~/.kube/config
multipass launch --name node1
multipass exec node1 -- sudo snap install microk8s --classic
multipass exec node1 -- sudo usermod -a -G microk8s ubuntu
multipass exec node1 -- sudo chown -f -R ubuntu ~/.kube
microk8s add-node
multipass exec node1 -- sudo microk8s join xxx.xxx.xxx.xxx:port/d008396d18bf5c02916190063a90a055/d2b3c4a95057

I use microk8s kubectl get nodes work. but use microk8s kubectl get nodes and it’s not work after I reboot. I get this error:

Unable to connect to the server: dial tcp 172.17.90.120:16443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

I use “microk8s inspect”. FAIL: Service snap.microk8s.daemon-kubelite is not running

Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver-kicker is running
 FAIL:  Service snap.microk8s.daemon-kubelite is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-kubelite
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting juju
  Inspect Juju
Inspecting kubeflow
  Inspect Kubeflow

Building the report tarball
  Report tarball is at /var/snap/microk8s/2695/inspection-report-20220106_040606.tar.gz
An error occurred when trying to execute 'sudo microk8s.inspect' with 'multipass': returned exit code 1.

reinstall is ok, but I can’t reinstall every time when I get this problem. can help? thanks.