Skip to content

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.

Sign up for GitHub

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

Closed
wants to merge 2 commits into from
Closed

DOCS-4493: Cover DNS error #4722

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a3143e4
DOCS-4493: Cover DNS error
npentrel Oct 23, 2025
ed99bf4
Add to common errors
npentrel Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/dev/tools/common-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,28 @@ The limit applies to calls through both WebRTC and direct gRPC connection, that

Try to find bottlenecks in scripts or modules that are hitting APIs for the machine in loops. You can check operations and sessions for a machine on its **CONTROL** tab at the bottom of the screen. To adjust the per-resource limit for modules, you can set the `VIAM_RESOURCE_REQUESTS_LIMIT` [environment variable on your machine](/manage/reference/viam-agent/#environment-variables-for-viam-server) to a positive integer higher than the default, 100.

### transport: Error while dialing: dial tcp: lookup app.viam.com

**Full Error:**

```sh {class="command-line" data-prompt="$" data-output="1-10"}
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: lookup app.viam.com on [::1]:53: read udp [::1]:<random ports>->[::1]:53: read: connection refused"
```

**Description**:

This error occurs due to congestion while different machine processes compete for bandwidth.
Copy link

@aldenh-viam aldenh-viam Oct 23, 2025

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.

Copy link
Collaborator Author

@npentrel npentrel Oct 23, 2025 •
edited
Loading

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?

Copy link

@aldenh-viam aldenh-viam Oct 23, 2025

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.

Copy link
Collaborator Author

@npentrel npentrel Oct 24, 2025 •
edited
Loading

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


**Solution:**

This error is usually harmless and may resolve on its own.
Copy link

@aldenh-viam aldenh-viam Oct 23, 2025

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.


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):
Copy link

@aldenh-viam aldenh-viam Oct 23, 2025

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.


```json
{ "forward_system_logs": "socks-forwarder" }
```

## Other common errors

### Accidental deletion of machines, locations, organizations, or accounts
Expand Down
2 changes: 1 addition & 1 deletion docs/manage/reference/viam-agent/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,7 +327,7 @@ If the highest-priority network is not available (or, if `turn_on_hotspot_if_wif
<!-- prettier-ignore -->
| Name | Type | Required? | Description |
| ---------- | ---- | --------- | ----------- |
| `forward_system_logs` | string | Optional | Enable forwarding of system logs (journald) to the cloud. A comma-separated list of SYSLOG_IDENTIFIERs to include, optionally prefixed with "-" to exclude. "all" is a special keyword to log everything. Examples: `"kernel,tailscaled,NetworkManager"` or `"all,-gdm,-tailscaled"`. Default: `""` (disabled). |
| `forward_system_logs` | string | Optional | Enable forwarding of system logs (journald) to the cloud. A comma-separated list of SYSLOG_IDENTIFIERs to include, optionally prefixed with "-" to exclude. "all" is a special keyword to log everything. Examples: `"kernel,tailscaled,NetworkManager,sock-forwarder"` or `"all,-gdm,-tailscaled"`. Default: `""` (disabled). |
| `logging_journald_runtime_max_use_megabytes` | integer | Optional |Set the temporary space limit for logs. `-1` to disable. Default: `512` (512 MB). |
| `logging_journald_system_max_use_megabytes` | integer | Optional | Sets the maximum disk space `journald` will use for persistent log storage. `-1` to disable. Default: `512` (512 MB). |
| `os_auto_upgrade_type` | string | Optional | Manage OS package updates using Viam by setting this field. Installs the `unattended-upgrades` package, and replace `20auto-upgrades` and `50unattended-upgrades` in <FILE>/etc/apt/apt.conf.d/</FILE>, with an automatically generated Origins-Pattern list that is generated based on that of `50unattended-upgrades`. Custom repos installed on the system at the time the setting is enabled will be included. Options: `"all"` (automatic upgrades are performed for all packages), `"security"` (automatic upgrades for only packages containing `"security"` in their codename (for example `bookworm-security`)), `"disable"` (disable automatic upgrades), `""` (do not change system settings). Default: `""`. |
Expand Down
Loading