Closed FaintGhost closed 6 months ago
fI have the same fault
same problem, netclinet does not pull config automatically in v12.2
ive discovered a similar issue with one of our 'server 2012 r2' machines, our issue i have found is whenever the node loses internet access and disconnects from the MQTT, and then it reconnects when the internet returns, its not reconnecting properly so the node shows as offline even though, you can ping the node no problem, i just simply restart the netclient service and it returns to normal no problem
Some of nodes (in China, perhaps behind the GFW) can join the network with no problem, all nodes can ping each other with no problem. But after a while, all chinese nodes status will first become to warning and then become to error. I saw the netclient.service logs in error node, it is different from normal node.
Can confirm. I met the same problem.
I ended up just adding a system timer similar to how it was done in v0.9.x, which for some reason is not present any more. Commit that removed it as part of #645: https://github.com/gravitl/netmaker/commit/443ed80e4d27d208134795e603aa8f166f7af017
Fix:
sudo nano /etc/systemd/system/netclient-pull.service
[Unit]
Description=Network Check
Wants=netclient.timer
[Service]
Type=simple
ExecStart=/usr/sbin/netclient pull -n all
[Install]
WantedBy=multi-user.target
sudo nano /etc/systemd/system/netclient.timer
[Unit]
Description=Calls the Netmaker Mesh Client Service
Requires=netclient.service
[Timer]
Unit=netclient-pull.service
OnCalendar=*:*:0/15
[Install]
WantedBy=timers.target
sudo systemctl enable netclient.timer
sudo systemctl start netclient.timer
same with netmaker server 0.14.1 running on docker. it worked perfectly after addin 4 nodes. Issues began when i added a windows 10 node (Sever network slowdown on the machine that had to be removed). Since then almost every node i add brings this issue. Restarts and reinstalls of client does not work. Will try a reinstall of server if issues persist, worsen or inhibit my use case
Please try it on latest version
Contact Details
zhang.yaowei@live.com
What happened?
I built a small mesh net with about 8 nodes. Some of nodes (in China, perhaps behind the GFW) can join the network with no problem, all nodes can ping each other with no problem. But after a while, all chinese nodes status will first become to warning and then become to error. I saw the
netclient.service
logs in error node, it is different from normal node. If I manuall do thenetclient pull
then the error node will become healthy again but for a while become warning and error again. I don't know what the problem is. Now I wrote a shell loop runnetclient pull
, but it's not a good solution. Could some one help me to solve this problem?logs of normal working nodes:
Version
v0.12.2
What OS are you using?
Linux
Relevant log output
Contributing guidelines