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

Enable an always up option. #182

Closed
Leopere opened this issue Jan 4, 2022 · 6 comments
Closed

Enable an always up option. #182

Leopere opened this issue Jan 4, 2022 · 6 comments

Comments

@Leopere
Copy link

Leopere commented Jan 4, 2022

It seems that the wiretrustee up command needs ran at regular intervals to ensure that the service never disconnects without any warning and self-healing. Is it possible to have a baked-in option to auto-heal the connection?

@braginini
Copy link
Contributor

Hey @Leopere
What version are you using?
In the recent versions we do self-healing and the only time the client app should stop is when it tried to connect unsuccessfully for 3 days in a row.

If you are using the latest version (0.3.2) then there must be a bug

@Leopere
Copy link
Author

Leopere commented Jan 29, 2022

ok good to know, I tend to update frequently and I'm doing it from the Ubuntu repo so it should have the latest.

@Leopere Leopere closed this as completed Jul 4, 2022
@Leopere Leopere reopened this Aug 20, 2022
@Leopere
Copy link
Author

Leopere commented Aug 20, 2022

Being revisited by this wonderful gem, I really want to stay with Netbird its such a useful tool but I'm getting to a point where I'm losing my mesh about once every 12 hours or so and its becoming very functionality inhibitive. I'm running a docker swarm over this mesh and its consistently breaking my GlusterFS mounts. Pls halp!

Daemon version: 0.8.6
CLI version: 0.8.6
Daemon status: Connected
Management: Connected
Signal:  Connected
NetBird IP: 100.64.0.214/24
Interface type: Kernel
Peers count: 10/21 Connected

About half of these are offline because they're set to only boot on demand however it often ends up with individual nodes in a split network mesh.

@mlsmaycon
Copy link
Collaborator

Hi @Leopere, sorry to hear that you are running into these issues.

I would like to get more information from your setup to troubleshoot the issue. Is it possible for you to reach out to me on our slack? this will make things much faster to check.

@Leopere
Copy link
Author

Leopere commented Aug 20, 2022

Oh sure yes I'll pop in over the next couple days I need this fixed if possible sooner than later I just recently upgraded to 0.8.6 and that's about when it started to melt. It seems my hybrid mesh between 20 something local devices on my LAN and 2 or three in the cloud at DigitalOcean.

The fix band-aide currently has been to netbird down && netbird up a few times until Error: unable to get daemon status: rpc error: code = Unknown desc = reset connection stops being the response and magically everything is healed. Then netbird status seems to show clients being added. In this scenario then I just need to unmount and remount my GlusterFS mounts and everything is back again.

@mlsmaycon
Copy link
Collaborator

the issue was caused by a race condition in our signal system, which was fixed here in #431

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

3 participants