DOCS-4171: Add troubleshooting for error when webrtc, mDNS, and gRPC fail #4742
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viambot
added
the
safe to build
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
|
@allisonschiang is this good to merge? |
Author
@npentrel the "failed to connect to robot within time limit" log is new with another PR I have up right now so I wanted to merge both at the same time! Not a big deal but in case the exact wording of the log gets changed in review I wanted to update it here too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of a project to improve error logging, I want to link the error: "Failed to connect to robot within time limit. Check network connection and try again. See http://docs.viam.com/dev/tools/common-errors/#conn-time-out" for troubleshooting steps" to some networking steps for debugging. Because the steps are already on the docs, I'm just moving the steps into their own section and then linking both the existing error and my new error to that networking section
The git changes looks really weird because im moving the network debugging text to just after the "Unable to create PeerConnection with module" so it shows me deleting it and re-adding it after but my changes have nothing to do with peerconnection stuff
Changes include adding a "failed to connect to robot" section, creating a network debugging section, and linking the "failed to connect to robot" and "Connection establishment failed" to this section
in conjunction with RDK log improvement: viamrobotics/rdk#5466