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.

kubelite fills syslog

See original GitHub issue

Hi I run 4 x Raspi Pi 4b on Ubuntu 20.04.3 and I get all 30 seconds this logs. Im not sure if its problematic. But it would be cool to stop it that the SD cards dont break this fast. Does someone has a clue?

Sep 20 21:13:56 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:13:56.721384    1787 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/2347/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Sep 20 21:13:56 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:13:56.721414    1787 clientconn.go:948] ClientConn switching balancer to "pick_first"
Sep 20 21:14:30 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:14:30.651939    1787 client.go:360] parsed scheme: "passthrough"
Sep 20 21:14:30 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:14:30.652097    1787 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/2347/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Sep 20 21:14:30 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:14:30.652155    1787 clientconn.go:948] ClientConn switching balancer to "pick_first"
Sep 20 21:15:01 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:01.432118    1787 client.go:360] parsed scheme: "passthrough"
Sep 20 21:15:01 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:01.432276    1787 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/2347/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Sep 20 21:15:01 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:01.432338    1787 clientconn.go:948] ClientConn switching balancer to "pick_first"
Sep 20 21:15:32 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:32.614834    1787 client.go:360] parsed scheme: "passthrough"
Sep 20 21:15:32 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:32.617552    1787 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/2347/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Sep 20 21:15:32 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:15:32.617647    1787 clientconn.go:948] ClientConn switching balancer to "pick_first"
Sep 20 21:16:09 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:16:09.832257    1787 client.go:360] parsed scheme: "passthrough"
Sep 20 21:16:09 k8s-1 microk8
s.daemon-kubelite[1787]: I0920 21:16:09.832391    1787 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/2347/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Sep 20 21:16:09 k8s-1 microk8s.daemon-kubelite[1787]: I0920 21:16:09.832441    1787 clientconn.go:948] ClientConn switching balancer to "pick_first"

inspection-report-20210920_211945.tar.gz

Issue Analytics

State:
Created 2 years ago
Comments:5

Top GitHub Comments

1reaction

balchuacommented, Sep 23, 2021

Ok so setting it to --v 0 will only show critical logs. What you are seeing without setting any --v is the default verbosity of kubernetes control plane components.

But if you want to preserve your storage device maybe setting you journal to volatile as described here. https://www.freedesktop.org/software/systemd/man/journald.conf.html

This is done by editing /etc/systemd/journald.conf setting Storage=volatile

0reactions

kanimarucommented, Sep 27, 2021

–v 0 was also more logs somehow ill go with Storage=volatile that works for me thx

Top Results From Across the Web

1.23 - HA Disabled - Syslog flood with kubelite logs ... - GitHub

Hello, I'm currently upgrading my Microk8s to the lastest 1.23 version. Installed with a snap command : sudo snap install microk8s ...

Kubernetes Log Forwarding with Syslog - IBM

Learn how to forward container logs from a Kubernetes cluster in the IBM Cloud Container Service to a remote syslog server.

Exporting Kubernetes events to Syslog | by Christian Frank

Rancher logging will scrape all output from all pods, including our events, and send them to Syslog, or whatever destination you've configured.

sitemap_1.xml - Discuss Kubernetes

... discuss.kubernetes.io/t/reduce-syslog-messages-created-removed-slice/9591 ... t/new-install-of-microk8s-fails-to-run-kubelite/16659 2021-07-11T15:31:02Z ...

Configuring MicroK8s services

The kubelite daemon runs as subprocesses the scheduler, controller, proxy, kubelet, and apiserver services. Each of these individual services can be ...