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.

kubelet logs and kube-apiserver logs are empty

See original GitHub issue

Hi, We run a microk8s 1.19/stable classic. We had a major incident tonight, all pods restarted @ 22:12 UTC. I am trying to find the root cause of the problem. I expect to find logs of kubelet and api-server through journald. However, logs are empty.

sysadmin@myserver:/var/snap/microk8s/common/var$ sudo journalctl -u kube-apiserver
-- Logs begin at Sat 2020-10-10 15:06:06 UTC, end at Tue 2020-10-20 11:49:56 UTC. --
-- No entries --

sysadmin@myserver:/var/snap/microk8s/common/var$ sudo journalctl -u kubelet
-- Logs begin at Sat 2020-10-10 15:06:06 UTC, end at Tue 2020-10-20 11:56:17 UTC. --
-- No entries --

How can I get logs ? Any clue is welcome Thanks AF

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

ktsakalozoscommented, Oct 20, 2020

Hi @arnoldfranz

microk8s inspect will print the names of all services in MicroK8s and will gather logs in a tarball. The two services you are looking for are snap.microk8s.daemon-apiserver and snap.microk8s.daemon-kubelet.

0reactions

ktsakalozoscommented, Oct 22, 2020

Thanks