mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Adguard no respond DNS request after certain Time - Docker Contener become Unealthy #4544
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#4544
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bartounet16 on GitHub (Jun 25, 2023).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux/ARM64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
0.107.32
Action
:~$ nslookup -debug -type=a 'www.free.fr' '10.0.0.250'
;; connection timed out; no servers could be reached
Expected result
Container runs normally
Actual result
nslookup failed for 0.0.0.0:53 after certain time
Contener becom Unealthy
Additional information and/or screenshots
023/06/23 19:10:29.288547 [info] AdGuard Home, version v0.107.32
2023/06/23 19:10:29.288580 [info] AdGuard Home updates are disabled
2023/06/23 19:10:29.289872 [info] tls: using default ciphers
2023/06/23 19:10:29.292120 [info] safesearch default: reset 253 rules
2023/06/23 19:10:29.341228 [info] Initializing auth module: /opt/adguardhome/work/data/sessions.db
2023/06/23 19:10:29.341298 [info] auth: initialized. users:1 sessions:3
2023/06/23 19:10:29.341309 [info] web: initializing
2023/06/23 19:10:29.359633 [info] dnsproxy: cache: enabled, size 4096 b
2023/06/23 19:10:29.359645 [info] dnsproxy: max goroutines is set to 300
2023/06/23 19:10:29.359769 [info] AdGuard Home is available at the following addresses:
2023/06/23 19:10:29.359860 [info] go to http://127.0.0.1:80
2023/06/23 19:10:29.359866 [info] go to http://172.24.0.2:80
2023/06/23 19:10:29.506545 [info] dnsproxy: starting dns proxy server
2023/06/23 19:10:29.506561 [info] Ratelimit is enabled and set to 20 rps
2023/06/23 19:10:29.506564 [info] The server is configured to refuse ANY requests
2023/06/23 19:10:29.506567 [info] dnsproxy: cache: enabled, size 4194304 b
2023/06/23 19:10:29.506571 [info] dnsproxy: max goroutines is set to 300
2023/06/23 19:10:29.506589 [info] dnsproxy: creating udp server socket 0.0.0.0:53
2023/06/23 19:10:29.506663 [info] dnsproxy: listening to udp://[::]:53
2023/06/23 19:10:29.506672 [info] dnsproxy: creating tcp server socket 0.0.0.0:53
2023/06/23 19:10:29.506695 [info] dnsproxy: listening to tcp://[::]:53
2023/06/23 19:10:29.507321 [info] dnsproxy: entering udp listener loop on [::]:53
2023/06/23 19:10:29.507373 [info] dnsproxy: entering tcp listener loop on [::]:53
2023/06/24 19:10:29.758499 [info] saving contents of filter #1 into /opt/adguardhome/work/data/filters/1.txt
2023/06/24 19:10:29.758721 [info] updated filter 1: 1072167 bytes, 54152 rules
2023/06/24 19:10:30.965258 [info] got status code 403 from https://curben.gitlab.io/malware-filter/urlhaus-filter-agh-online.txt, skip
2023/06/24 19:10:30.965377 [info] Failed to update filter https://curben.gitlab.io/malware-filter/urlhaus-filter-agh-online.txt: got status code 403, want 200
2023/06/24 19:10:31.352596 [info] saving contents of filter #1665227529 into /opt/adguardhome/work/data/filters/1665227529.txt
2023/06/24 19:10:31.372661 [info] updated filter 1665227529: 46721 bytes, 2570 rules
2023/06/24 19:10:35.157537 [info] Updated filter #1. Rules: 54012 -> 54152
2023/06/24 19:10:35.157551 [info] Updated filter #1665227529. Rules: 2724 -> 2570
.
---.
13a0ed4c5bcecf704df7d33efdee3bb2527245d3c099d4a029ae7aad86168dee
@bartounet16 commented on GitHub (Jul 1, 2023):
This morning same problem..
Adguard no respond DNS request after certain Time
Need to relaunch contener
1 month problem exists ... and no solved
@julichan commented on GitHub (Jul 2, 2023):
Same problem with me. It became so frequent that i had no choice but to turn it off and go back to another dns...
I don't think it's related to this 403 as i have a clean log. the only thing i know is that docker marks the container as unhealthy and a lot of website becomes unvailable and android does not even consider the wifi having internet anymore.
All this clears up with a container restart until it happens again.
@bundyland commented on GitHub (Jul 3, 2023):
Guys, this is a problem which was already discussed here and here.
Till the Adguard team has located and fixed the problem, you should downgrade to version v.0.107.29.
@bartounet16 commented on GitHub (Jul 3, 2023):
Thanks a lot
So the problem is known and identified but not solved and we have to downgrade to V.0.107.29
how to downgrade on a Stack Docker ... and block the update with watchtower ?
Do you have an idea of the problem and the resolution time?
@bundyland commented on GitHub (Jul 4, 2023):
I use docker compose and have put the following in the docker-compose.yml:
services:
adguardhome:
container_name: adguardhome
restart: always
image: adguard/adguardhome:v0.107.29 (instead of :latest)
healthcheck:
disable: true
...
Like that docker will always use v0.107.29 and will never update to a more recent version.
Hope this helps.
@Freebase394 commented on GitHub (Jul 4, 2023):
Hi there,
Recently, about a month ago, I've been noticing some anomalous behavior, somehow always on the latest (having all updates up to date) AdGuardHome. My raspbery Pi 3 b+ would always get unresponsive after some time randomly.
A few days ago (3 - 4 days) I upgraded to x64 intel and the same thing happened.
Can someone help me, and confirm this logical reasoning, please ?
I have creatd this issue:
#5964
What else can I do to make sure all the scenarios are right and correct?
@bigwookie commented on GitHub (Jul 4, 2023):
#5962 This looks to be the same issue.
@julichan commented on GitHub (Jul 4, 2023):
thanks trying v0.107.29 too
@ainar-g commented on GitHub (Jul 12, 2023):
@bartounet16, could you please try v0.107.34?
@n0rt0nthec4t commented on GitHub (Jul 12, 2023):
Just found this thread and on v0.107.34.. Docker container gets reported as 'unhealthy" in portainer
@BlackScript commented on GitHub (Jul 13, 2023):
same in current beta
v0.108.0-b.41 shows in portainer as unhealthy
@bigwookie commented on GitHub (Jul 13, 2023):
Running this @ainar-g and is working well no crashes, no spiking CPU and DNS requests are still running.
@n0rt0nthec4t @BlackScript the docker health in portainer and the Synology Container manager are staying up saying healthy. I have setup the container as bridged so expect you might be running on a different system.
@brknkfr commented on GitHub (Jul 13, 2023):
I have the same problem starting from version 0.107.32. Version 0.107.31 seems to work fine ...
@julichan commented on GitHub (Aug 14, 2023):
Has anyone tried 0.107.34 ? I've seen on another thread that related problems have been fixed but i m unsure if it is the same bug.
Some of you a reporting it is still unhealthy but @bigwookie says otherwise. what it the actual status ?
@ainar-g commented on GitHub (Aug 14, 2023):
OP has indicated in another issue that the problem has been resolved, see https://github.com/AdguardTeam/AdGuardHome/issues/5896#issuecomment-1638756252. Do not forget that a full image/container re-creation may be necessary, as documented in the release notes.
I'll close this issue, as it seems to have been the same as the one linked above.