check-supernodes sequence over tunnel #2002
Labels
enhancement
New feature or request
Comments
|
I think this may be the value that needs to be adjusted. Maybe I am wrong, but this looks like the code that ultimately calls check-supernodes after boot. |
Adding additional delay before the startup tasks did not resolve the issue. In fact, the 2 minute delay results in the tunnel not connecting until after the 2 minutes has passed. Adding delay to the start up period tasks also delays the tunnel connection by the same amount of time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After rebooting the node, some times DNS names to not resolve. I suspect that check-supernodes is running before the tunnel server & client nodes have fully connected. Issue with happen when tunnel is slow to connect. After reboot, If it takes longer than 1-2 minutes for the tunnel client node to resolve the DNS name of the tunnel server neighbor node, DNS discovery will fail until the next hour when "check-supernodes" runs via crontab. If i end up in the failed state, manually running "cd /etc/cron.hourly/ ; ./check-supernodes" from ssh resolves the issue immediately.
Expected behavior
If tunnels are enabled on the client, and the system has booted. After the client node connects and has resolved the server nodes name. Then check-supernodes should execute.
Support data
Please add the support data for all nodes mentioned in this bug report (Required)
Screenshots
Please include a screenshot of your system information (if possible) if the specific system environment is relevant to the bug.
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: