canonical / microk8s

MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.

Home Page:https://microk8s.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cluster down kine.sock connection refused

JasonPulse opened this issue · comments

Summary

Came home to have my 2 node cluster down with both nodes reporting the error below for kubelite service
May 16 06:11:30 ubuntu microk8s.daemon-kubelite[6065]: W0516 06:11:30.766110 6065 logging.go:59] [core] [Channel #7 SubChannel #9] grpc: addrConn.createTransport failed to connect to {Addr: "unix:///var/snap/microk8s/6787/var/kubernetes/backend/kine.sock:12379", ServerName: "kine.sock:12379", }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/snap/microk8s/6787/var/kubernetes/backend/kine.sock:12379: connect: connection refused"

What Should Happen Instead?

Running cluster

Reproduction Steps

Unknown at this time, assumed something to do with a snap refresh.

Introspection Report

System is unstable 20-30 seconds to echo back typing with microk8s trying to start, tar is with microk8s stopped, if requested I can provide files from /var/snap/microk8s/current/var/kubernets/backend as there is no sensitive data running on cluster

Would like to know why this happened as we have several clusters running the same things and with them all failing for a different issue of nf_conntrack having another issue to go back to will not be fun.

inspection-report-20240516_151937.tar.gz

After about 7 hours I was able to get a Tar from running microk8s
inspection-report-20240516_223539.tar.gz