-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[error] handling tcp: closing conn: use of closed network connection - repeat errors #4065
Comments
Providing more information.. Log file from Beta version.... (same issue)
|
Thanks for the report! It's most probably a logging issue rather than an actual error. We'll fix it in v0.107.3. |
Updates AdguardTeam/AdGuardHome#4065. Squashed commit of the following: commit 89b65c9 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Jan 17 18:40:50 2022 +0300 proxy: imp code commit 344c528 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Jan 17 18:20:53 2022 +0300 all: fmt, imp logs
@gspannu, the version |
I'll close this issue for now. Please feel free to write if you have any other problems and can't find a solution. |
Updates AdguardTeam#4065. Squashed commit of the following: commit d65d2e3 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Mon Jan 17 18:47:17 2022 +0300 all: upd dnsproxy
Issue Details
Multiple error lines relating to tcp:closing conn, use of closed network connection - being recorded in log file.
Version of AdGuard Home server:
v0.108.0-a.24+e9c59b09, beta, release - in all versions
How did you install AdGuard Home:
GitHub release
CPU architecture:
linux_amd64
Operating system and version:
Debian x11 - running on Cloud hosted VPS
Here is my log file...
I have tried using stable, beta, edge releases - but issue appears in all versions.
Using amd64 version on a Debian x11 server machine, hosted in the Cloud.
The bug my be related to an earlier reported bug (but presumably fixed)
#4042
The text was updated successfully, but these errors were encountered: