#4573·microk8s

Microk8s service is not starting

Author: MurugeshbvCreated Jul 15, 2024Updated Sep 7, 2026
Labelsinactive

Summary

Microk8s service is not starting and found that (**FAIL: Service snap.microk8s.daemon-kubelite is not running) the version of Microk8s we are using is
MicroK8s v1.26.15 revision 6673

Kubetcl Version : Client Version: v1.30.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3

we have restarted microk8s also but still it didn't worked.

iam pasting the console below here and also attached snapshot and inspection report as well. Let us know,if you need any additional details

**root@rmmycldtl201881:# microk8s start root@rmmycldtl201881:# microk8s status microk8s is not running. Use microk8s inspect for a deeper inspection. root@rmmycldtl201881:# kubectl get nodes E0715 14:07:50.350598 82577 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:16443/api?timeout=32s": dial tcp 127.0.0.1:16443: connect: connection refused E0715 14:07:50.351146 82577 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:16443/api?timeout=32s": dial tcp 127.0.0.1:16443: connect: connection refused E0715 14:07:50.353129 82577 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:16443/api?timeout=32s": dial tcp 127.0.0.1:16443: connect: connection refused E0715 14:07:50.353422 82577 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:16443/api?timeout=32s": dial tcp 127.0.0.1:16443: connect: connection refused E0715 14:07:50.354621 82577 memcache.go:265] couldn't get current server API group list: Get "https://127.0.0.1:16443/api?timeout=32s": dial tcp 127.0.0.1:16443: connect: connection refused The connection to the server 127.0.0.1:16443 was refused - did you specify the right host or port? root@rmmycldtl201881:# microk8s inspect Inspecting system Inspecting Certificates Inspecting services Service snap.microk8s.daemon-cluster-agent is running Service snap.microk8s.daemon-containerd is running FAIL: Service snap.microk8s.daemon-kubelite is not running For more details look at: sudo journalctl -u snap.microk8s.daemon-kubelite Service snap.microk8s.daemon-k8s-dqlite is running Service snap.microk8s.daemon-apiserver-kicker is running Copy service arguments to the final report tarball Inspecting AppArmor configuration Gathering system information Copy processes list 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 openSSL information to the final report tarball Copy snap list to the final report tarball Copy VM name (or none) to the final report tarball Copy current linux distribution to the final report tarball Copy network configuration to the final report tarball Inspecting kubernetes cluster Inspect kubernetes cluster Inspecting dqlite Inspect dqlite

Building the report tarball Report tarball is at /var/snap/microk8s/6673/inspection-report-20240715_140838.tar.gz**

image inspection-report-20240715_140838.tar.gz