https://netmaker.org logo
Join Discord
Powered by
I have been playing around with this. on a fresh d...
# client
b
I have been playing around with this. on a fresh debian vm this also happens. BUT only if I install the client via apt from the repo. Loading the binary from GitHub and simply doing netclient install make the magic happen. No Healthy->Warning->Error over 6h now, while from the repos this happens in 60min. Any Idea? I would really like to not manually install and update netclient for all nodes.
j
can you give recreation steps for testing? would like to replicate this
@bored-island-21407 @echoing-controller-96073
@bright-eye-43554 can you provide replication steps so we can recreate this? Would help track down the issue
this is for a fresh client install, not an upgrade, right?
b
this is complete fresh :=) debian VM running on unraid.
I did, at first follow the steps from the website (adding repos and updating etc.) than joined my network. All is fine for some minutes and I can ping around. After some time and for no obvious reason the state in the dasboard is degrading. However, parts of the connectivity remain (can still reach the node from external - android- client)
oh on thing, that node (the one that is degrading) is an egress node for my lan at home
the VM config.
btw i have a very similar issue on Windows. My wifes laptop, where is just downloaded the .exe and installed from GUI works like a charm. On my desktop (win 11) I had similar issues but those are somehow infrequent and I have not found a way to reproduce them.
b
the status in the UI reflects mq connectivity. It is possible for a node in error state to have full connectivity with all of its peers. If the network changes (addition or deletions of node, for example) the node without mq connectivity will not receive those updates
b
but why is that behaviour different in manual install vs. repo install. Are there any log that reflect mq state in win/linux?
j
@echoing-controller-96073 please test
e
ok. will do
PreviousNext
Powered by