-
Notifications
You must be signed in to change notification settings - Fork 48
DOCS-4493: Cover DNS error #4722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the main thing here is to just verify your internet connection is stable and usable (outside of Viam software, e.g. confirm you can browse the web, ping, etc.). The socks-forwarder bits will not be relevant to the majority of users.
| **Description**: | ||
| This error occurs due to congestion while different machine processes compete for bandwidth. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only my hypothesis that error appears when your internet connection becomes flaky (and socks-forwarder, if you choose to connect through it, by design will be), but it's not 100% verified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, what do you suggest we should tell the user about this then?
Should I just close the PR and we leave it out or would you like to confirm your hypothesis?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Best I have for now is just to verify your internet connection is stable and if it's not, the error should go away once it is. Up to you if you feel that's sufficient, or just leave it out for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok I'll leave it out for now since we can't describe the error
| This error is usually harmless and may resolve on its own. | ||
| To get more logs, you can enable forwarding system logs for SOCKS, by adding the following to your [`viam-agent` system configuration](/manage/reference/viam-agent/#system-configuration): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not everyone will be running socks-forwarder.
| **Solution:** | ||
| This error is usually harmless and may resolve on its own. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Going with the hypothesis, yes this appears to resolve on its own once the internet connection returns to a stable/usable state.

No description provided.