Tailscale up command results in infinite loop of connection status #128
Comments
|
Later edit: spoke too soon, on the next run |
I've noticed it isn't a 100% repro, sometimes it works, for now I've fallen back to the default (which I believe is 1.42.0) - on the upside I'm happy to know that it isn't just me experiencing the looped log/action output. |
|
@patrickod - do you know if this looks to be a github action specific issue or something in core tailscale that might need to be addressed there? |
|
@seanmcne it is possible that a recent change in the client might be at issue here but without more detailed logs is it hard to tell. Would you be able to share with us the log output from a failed run that you have observed? Separately we recently released 1.66.4 which may address this issue. Is this bug reproducible with this most recent version? |
|
I tried Here is the workflow I used (note that I am also trying to use a Tailscale Exit Node): which produced the following logs: 442 lines of logs |
|
The error is coming from this action trying to download the tailscale package from @Vlaaaaaaad I notice in your tailnet you have a DNS server running on one of the nodes, configured as a nameserver in https://login.tailscale.com/admin/dns. And your ACLs don't seem to allow traffic from I was not able to reproduce this with the same workflow file that you have. |
|
@awly yup, editing the ACL to allow I am a bit surprised though: when the DNS server is not accessible I would've expected the fallback DNS servers (Google's DNS servers in my case) to be used 🤔 |
That's a good point, I'm not sure why it doesn't work that way. @Vlaaaaaaad could you file a separate bug in http://github.com/tailscale/tailscale for this DNS fallback issue please? |
|
@seanmcne could you try setting up a new node outside of github actions with |
@awly it seems there's already an issue for "DNS hangs when ACL blocks traffic to DNS servers and when Split DNS is used". Would you rather I comment on that issue something along the lines of "this also happens when Split DNS is not used" or would you rather I create a new "Fast-fail DNS when ACLs block traffic to the DNS server" issue? |
|
@Vlaaaaaaad I think it's a separate issue: when you have multiple global nameservers (not split DNS), the query should time out faster and fall back to other configured nameservers. |
|
@awly I think this is the worst bug report I ever submitted in my life, but I did it: tailscale/tailscale#12403 I tried to find easier ways to reproduce this but I failed to find any easily testable options. |
|
@awly it looks like I'm unable to repro, I have the log for tailscale captured now on every single github action run, just in case this happens again. It sounds like the path around downloading the package sounds like the most likely place to look at since it does explain how it's intermittent - I also was noticing some DNS issues around the same point-in-time (which seem to have cleared up without intervention) that cause seems to make sense to me. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running the following in a github action, in previous versions it typically connects then when I call the up command again with an --exit-node value it will sometimes result in this constant repeating log of all 0's for many minutes until it times out. Am I using the action incorrectly given recent updates?
The text was updated successfully, but these errors were encountered: