-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Adguard no respond DNS request after certain Time - Docker Contener become Unealthy #5933
Comments
This morning same problem.. 1 month problem exists ... and no solved |
Same problem with me. It became so frequent that i had no choice but to turn it off and go back to another dns... |
Thanks a lot |
I use docker compose and have put the following in the docker-compose.yml: services: Like that docker will always use v0.107.29 and will never update to a more recent version. Hope this helps. |
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. Can someone help me, and confirm this logical reasoning, please ? I have creatd this issue: What else can I do to make sure all the scenarios are right and correct? |
#5962 This looks to be the same issue. |
thanks trying v0.107.29 too |
@bartounet16, could you please try v0.107.34? |
Just found this thread and on v0.107.34.. Docker container gets reported as 'unhealthy" in portainer |
same in current beta |
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. |
I have the same problem starting from version 0.107.32. Version 0.107.31 seems to work fine ... |
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. |
OP has indicated in another issue that the problem has been resolved, see #5896 (comment). 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. |
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
The text was updated successfully, but these errors were encountered: