as i don't know if I'm a fan of that lol

Thanks, I'll check tomorrow. Pretty sure it was a recent compose released with 0.8.3 as I started again with that build. Presumably I want client mode set to on

I recently upgraded my Netmaker from

0.8.2

to

0.8.4

... there really were no changes required except changing the tag for the docker image in my

docker-compose.yaml

file. I did so, did a

docker-compose pull && docker-compose up -d

... and everything worked as expectd. But then i noticed in the Netmaker UI (dashboard) my

netmaker

node is was in a

WARNING

state... I thought this odd, but couldn't find any problem in netmaker logs or by pinging all nodes. I looked a bit closer and saw that the node was a relay. So I removed the relay config, and the node became

HEALTHY

. I re-added the same relay config and still the node was OK. Tonight I noticed that

netmaker

node as now in an

ERROR

state... Once again, I removed the

relay

config, and readded, and it's

HEALTHY

again. I'm not seeing a problem, but I'm confused what this means or why it's happening and I see nothign in logs. Any tips on how to troubleshoot this more? I've just increased VERBOSITY on the netmaker container, so we'll see if I see anything, but so far the node has not get non-HEALTHY again.

I just moved the above message from #825071821594034196 because now I'm less curious and truly troubleshooting. I also had some kernel updates pending on my netmaker host. So I rebooted the host. Now, the

netmaker

node is not participating in any wireguard connections at all.

sudo wg show

shows nothing. netmaker logs just show other nodes checking in. I'm digging around but curious/concerned.

I did have

CLIENT_MODE: "contained"

but changed to "on" now i do get an error

netmaker                     | 2021/10/26 04:37:03 [netmaker] netmaker could not set peers on network MYNET
netmaker                     | 2021/10/26 04:37:03 [netmaker] netmaker file does not exist
netmaker                     | 2021/10/26 04:37:03 [netmaker] error occurred during server checkin: could not find any records
netmaker                     | 2021/10/26 04:37:03 [netmaker] completed a checkin call

Is there a config directory under

/etc/netclient

with files belonging to

MYNET

?

yep!

$ grep netclient docker-compose.yml
      - /etc/netclient/config:/etc/netclient/config
$ sudo ls -l /etc/netclient/config
total 16
-rwxr-xr-x 1 root root 1633 Oct 24 00:03 netconfig-MYNET
-rw-r--r-- 1 root root  177 Oct  3 22:57 nettoken-MYNET
-rw-r--r-- 1 root root   16 Oct  3 22:57 secret-MYNET
-rw-r--r-- 1 root root   44 Oct  3 22:57 wgkey-MYNET

I'm not sure if i was clear earlier... 1) after upgrading from 0.8.2 to 0.8.4, i got "WARNING/ERROR" for the netmaker node in UI (which I think just means it wasn't checking in, seems like WARNING is 5 minutes of no checkin, and error is 10 minutes, IIRC Alex's comments elsewhere, but I didn't realize this when i originall asked)... however, the node's wireguard was still functional... I suppose because it had already been configured with 0.8.2 2) after rebooting, i had no wireguard config and no errors in netmaker logs, and i was in

CLIENT_MODE: contained

3) then i changed to

CLIENT_MODE: on

and started seeing the

netmaker file does not exist

error

Have you tried making a new network since that change?

i'll try it now

uh... hmm... maybe netmaker is storing configs in a different path? and the upgrade required a path change which i missed?

because new network works

but i can't find the configs for it

yeah as of 0.8.4, the netmaker server stores it all in db

oh 😕

heh 🙂 that seems like a change missing from the release notes LOL

lol yeah, I'm not sure we thought it would be super necessary to cover as we were hoping the transition would be seamless, but ig not completely

Ah, is there something netmaker server attempts to do to import the netclient configs, or should they already be in the DB?

should be in db, but it "should" regenerate it on a check in as well

ok, so i should no longer need the

/etc/netclient/config

volume mount ?

correct

welp. that's interesting

how can we run a command on the server managed netclient? my netmaker server node is really unhappy. I would like to get it to pull from the server but not sure how to do that anymore

I'm very glad that it works with new networks, of course, that's painful for us early adopters when an upgrade doesn't work 🙂 I've seen a few changes as it relates to client mode on netmaker server... and I'm beginning to develop the general opinion that netmaker server probably shouldn't run the client itself... if a user wants that, maybe just run netclient on that node

right, but in order for UDP hole punching to work, if the user needs it, (which I use mostly) we need a wg interface on the server

So, if I ran a netmaker with

CLIENT_MODE: off

and a manually joined

netclient

on the same host, I still couldn't take advantage of UDP hole punching? Good to know if so...

right

Even if it my hacky way did work, of course, its more ideal if server ran it... simpler setup

yeah, we're not trying to make it harder I promise haha

🙂 I'm sure not! I was just talking with Alex about continued improvements yesterday.