AdguardTeam / AdguardTeam/AdGuardHome

One upstream timeout, not using others when parallel queries is selected

Aperta
#7,390 2 commenti 2 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [X] I have searched other issues and found no duplicates

- [X] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [X] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

0.107.53

### Action

Replace the following command with the one you're calling or a
description of the failing action:

Sometimes the AdGuard Home just stopped responding to queries.
WebUI working, query log shows no new records, it seems to just stop working all of a sudden.

The command line tool recorded the following logs:
i/o timeout or timeout: no recent network activity

I also have other upstream DNS servers, but AdGuard's query thread appears to be blocked due to one DNS server's timeout.

### Expected result

AdGuard Home gets responses from upstream servers and forwards them to clients.

### Actual result

client dig timed out.
AdGuard Home's WebUI shows no recent DNS entries. Debug level logging file shows ERROR - i/o timeout or timeout, not trying other servers. Already set to "parallel query".

### Additional information and/or screenshots

2024/10/30 02:37:48.070251 ERROR response received addr=https://cloudflare-dns.com:443/dns-query proto=udp status="requesting https://cloudflare-dns.com:443/dns-query: Get_0rtt \"https://cloudflare-dns.com:443/dns-query?dns=[redacted]\": timeout: no recent network activity"
2024/10/30 02:37:48.070276 ERROR response received addr=https://cloudflare-dns.com:443/dns-query proto=udp status="requesting https://cloudflare-dns.com:443/dns-query: Get_0rtt \"https://cloudflare-dns.com:443/dns-query?dns=[redacted]\": timeout: no recent network activity"
2024/10/30 02:37:48.070293 ERROR response received addr=https://cloudflare-dns.com:443/dns-query proto=udp status="requesting https://cloudflare-dns.com:443/dns-query: Get_0rtt \"https://cloudflare-dns.com:443/dns-query?dns=[redacted]\": timeout: no recent network activity"
2024/10/30 02:37:48.070293 ERROR response received addr=https://cloudflare-dns.com:443/dns-query proto=udp status="requesting https://cloudflare-dns.com:443/dns-query: Get_0rtt \"https://cloudflare-dns.com:443/dns-query?dns=\": timeout: no recent network activity"
2024/10/30 02:37:53.043377 ERROR response received addr=1.1.1.1:53 proto=udp status="exchanging with 1.1.1.1:53 over udp: read udp [ip]->1.1.1.1:53: i/o timeout"
2024/10/30 02:37:53.045551 ERROR response received addr=1.1.1.1:53 proto=udp status="exchanging with 1.1.1.1:53 over udp: read udp [ip]->1.1.1.1:53: i/o timeout"
2024/10/30 02:37:53.045573 ERROR response received addr=1.1.1.1:53 proto=udp status="exchanging with 1.1.1.1:53 over udp: read udp [ip]->1.1.1.1:53: i/o timeout"
2024/10/30 02:37:53.046651 ERROR response received addr=1.1.1.1:53 proto=udp status="exchanging with 1.1.1.1:53 over udp: read udp [ip]->1.1.1.1:53: i/o timeout"

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.