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

How do I debug pod error "failed to receive. \"waiting for init ready\". BrokenChannel" in k3s? #197

Open
Mossaka opened this issue Dec 22, 2023 · 0 comments

Comments

@Mossaka
Copy link
Member

Mossaka commented Dec 22, 2023

We've observed a recurring error in pod logs that states:

"Error: failed to create containerd task: failed to create shim task: Others("failed to receive. "waiting for init ready". BrokenChannel"): unknown"

This issue is known to be linked to specific problems (e.g., Issue #173). To effectively assist in debugging, we require detailed Containerd logs from affected users.

This issue serves as a guide for users on how to access and provide Containerd logs from k3s clusters.

Steps to Access Containerd Logs

Refer to k3s Documentation: The k3s logs FAQ provides general guidance on locating various logs within k3s.

Accessing Containerd Logs:

  • Utilize docker exec to enter your workload container.
  • Once inside, navigate to /var/lib/rancher/k3s/agent/containerd/containerd.log. This file contains the Containerd logs.
  • You might encounter log entries similar to ">>> running spin trigger".

Reporting

After locating the Containerd logs, please create a new issue and attach the relevant log excerpts. This will greatly assist in diagnosing and addressing the root cause of the error you're encountering.

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

1 participant