microk8s.daemon-kubelet fail to start in latest stable channel
See original GitHub issuePlease run microk8s.inspect
and attach the generated tarball to this issue.
inspection-report-20190925_123430.tar.gz
We appreciate your feedback. Thank you for using microk8s.
I use snap install microk8s --classic
to install microk8s
, kubelet fail to start with following error message from journal log:
sudo journalctl -u snap.microk8s.daemon-kubelet.service
Sep 25 10:49:53 guozhewei-clouddev.dyn.nesc.nokia.net systemd[1]: Started Service for snap application microk8s.daemon-kubelet.
Sep 25 10:49:53 guozhewei-clouddev.dyn.nesc.nokia.net microk8s.daemon-kubelet[7094]: iptables: Bad rule (does a matching rule exist in that chain?).
Sep 25 10:49:53 guozhewei-clouddev.dyn.nesc.nokia.net microk8s.daemon-kubelet[7094]: Waiting for containerd socket /var/snap/microk8s/common/run/containerd.sock to appear. (attempt 0)
Sep 25 10:49:55 guozhewei-clouddev.dyn.nesc.nokia.net microk8s.daemon-kubelet[7094]: Waiting for containerd socket /var/snap/microk8s/common/run/containerd.sock to appear. (attempt 1)
Sep 25 10:49:57 guozhewei-clouddev.dyn.nesc.nokia.net microk8s.daemon-kubelet[7094]: Waiting for containerd socket /var/snap/microk8s/common/run/containerd.sock to appear. (attempt 2)
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net sudo[7763]: PAM unable to dlopen(/usr/lib64/security/pam_unix.so): /snap/core/current/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/lib64/security/pam_unix.so)
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net sudo[7763]: PAM adding faulty module: /usr/lib64/security/pam_unix.so
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net sudo[7763]: root : PAM account management error: Module is unknown ; TTY=unknown ; PWD=/var/snap/microk8s/826 ; USER=root ; COMMAND=/snap/microk8s/826/bin/sed -i $ a --runtime-cgroups=/systemd/system.slice /var/snap/microk8s/826/args/kubelet
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net microk8s.daemon-kubelet[7094]: sudo: PAM account management error: Module is unknown
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net systemd[1]: snap.microk8s.daemon-kubelet.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net systemd[1]: snap.microk8s.daemon-kubelet.service: Failed with result 'exit-code'.
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net systemd[1]: snap.microk8s.daemon-kubelet.service: Service RestartSec=100ms expired, scheduling restart.
Sep 25 10:50:00 guozhewei-clouddev.dyn.nesc.nokia.net systemd[1]: snap.microk8s.daemon-kubelet.service: Scheduled restart job, restart counter is at 1.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (1 by maintainers)
Top Results From Across the Web
microk8s.daemon-kubelet fail to start in latest stable channel
I use snap install microk8s --classic to install microk8s , kubelet fail to start with following error message from journal log: sudo journalctl ......
Read more >Troubleshooting - MicroK8s
You may experience the API server being slow, crashing or forming an unstable multi node cluster. Such problems are often traced to low...
Read more >The apiserver/kubelet are inactive - microk8s
I have installed the 1.23 version of microk8s. There are 3 master and 3 worker nodes. The above messages are one node of...
Read more >Install a local Kubernetes with MicroK8s - Ubuntu
Ubuntu is an open source software operating system that runs from the desktop, to the cloud, to all your internet connected things.
Read more >How to Fix Kubernetes 'Node Not Ready' Error - Komodor
Common reasons for a Kubernetes node not ready error include lack of resources on the node, a problem with the kubelet (the agent...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m on CentOS 8, and yes, that fixes it for me. Tank you!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.