Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microk8s is not running, but some pods does #4594

Open
ZhouJian26 opened this issue Jul 31, 2024 · 2 comments
Open

Microk8s is not running, but some pods does #4594

ZhouJian26 opened this issue Jul 31, 2024 · 2 comments

Comments

@ZhouJian26
Copy link

Summary

I have a cluster in HA with MicroK8s version 1.29 stable. I found the cluster crashed for no apparent reason, and I can't figure out how to solve this problem. On each node, microk8s status says microk8s is not running. Use microk8s inspect for a deeper inspection. However, microk8s inspect indicates that everything is working fine.

I noticed that I'm unable to perform microk8s kubectl get nodes, which result with Error from server: rpc error: code = Unknown desc = query (try: 0): theid

I tried stopping and restarting MicroK8s on each node, and I also restarted all the servers multiple times.

I see that some services are running while others simply cannot start. The most common error I'm seeing is: error=rpc error: code = Unknown desc = query (try: 0): theid.

Commands like kubectl get namespace are working fine

Reproduction Steps

I'm unable to reproduce this cluster state with a brand new one.

Introspection Report

inspection-report-20240731_131206.tar.gz

Can you suggest a fix?

no, idea

Are you interested in contributing with a fix?

I do not have the skill to do it

@crypto-titan
Copy link

this is entirely valid I am getting the same thing:

ubuntu@stakepool-de-02:~$ kubectl get nodes -o wide
Error from server: rpc error: code = Unknown desc = query (try: 0): theid

2024-09-09T17:06:46.160808+00:00 stakepool-de-13 microk8s.daemon-kubelite[2692964]: W0909 17:06:46.160123 2692964 logging.go:59] [core] [Channel #1 SubChannel #3] grpc: addrConn.createTransport failed to connect to {Addr: "unix:///var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379", ServerName: "kine.sock:12379", }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379: connect: connection refused"
2024-09-09T17:06:46.241642+00:00 stakepool-de-13 microk8s.daemon-kubelite[2692964]: W0909 17:06:46.241539 2692964 logging.go:59] [core] [Channel #2 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "unix:///var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379", ServerName: "kine.sock:12379", }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379: connect: connection refused"
2024-09-09T17:06:46.511467+00:00 stakepool-de-13 microk8s.daemon-kubelite[2692964]: W0909 17:06:46.511330 2692964 logging.go:59] [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {Addr: "unix:///var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379", ServerName: "kine.sock:12379", }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/snap/microk8s/7180/var/kubernetes/backend/kine.sock:12379: connect: connection refused"
2024-09-09T17:06:47.910484+00:00 stakepool-de-13 agent[32789]: 2024-09-09 17:06:47 UTC | CORE | INFO | (pkg/logs/launchers/file/launcher.go:337 in handleTailingModeChange) | Tailing mode changed for file:/var/log/auth.log. Was: end: Now: beginning

It's happening on multiple servers.

@crypto-titan
Copy link

Ubuntu 24.04 MicroK8s 1.30.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants