-
Notifications
You must be signed in to change notification settings - Fork 415
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
Netbird is causing my laptop to kernel panic #1980
Comments
@ItIsGhastly , this seems duplicated from #1896, can you confirm if the issue happens only when there is a exit node route configured? Can you share the logs from the daemon service too? https://docs.netbird.io/how-to/troubleshooting-client#getting-client-logs |
client.log |
@mlsmaycon I am relatively certain, either way its not great when im in class and my laptops restarting randomly lol. client.log |
@mlsmaycon |
Hey folks, the PR #2025 seems to fix the issue. If anyone wants to try this build, you can use the binary from: https://github.com/netbirdio/netbird/actions/runs/9187529519/artifacts/1526014624 |
Hello Folks, the v0.27.9 has the fix for the crash. Thanks for your help testing the builds. |
context deadline exceeded is still popping up |
Describe the problem
Netbird is causing my Intel 2020 macbook air to kernel panic after a few minutes of being connected. I will attach the log that comes up after the laptop restarts. When i try to reconnect after the laptop restarts i get the error Dial service: context deadline exceeded.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
My laptop connects, and i can use the application fine to access my home network.
Are you using NetBird Cloud?
Self hosted quick start version.
NetBird version
netbird version gui 0.27.6
NetBird status -d output:
`Error: failed to connect to daemon error: context deadline exceeded
If the daemon is not running please run:
netbird service install
netbird service start
ghastly@MacBook ~ % netbird service start
"launchctl" failed with stderr: Warning: Expecting a LaunchAgents path since the command was ran as user. Got LaunchDaemons instead.
launchctl bootstrap
is a recommended alternative.Error: "launchctl" failed with stderr: Warning: Expecting a LaunchAgents path since the command was ran as user. Got LaunchDaemons instead.
launchctl bootstrap
is a recommended alternative.`Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
panic(cpu 2 caller 0xffffff801e8ab89b): userspace watchdog timeout….pdf
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: