mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
[error] handling tcp: closing conn: use of closed network connection - repeat errors #3342
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#3342
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 @gspannu on GitHub (Jan 2, 2022).
Originally assigned to: @ainar-g on GitHub.
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)
https://github.com/AdguardTeam/AdGuardHome/issues/4042
@gspannu commented on GitHub (Jan 2, 2022):
Providing more information..
Log file from Beta version.... (same issue)
Public IP addresses masked
@ainar-g commented on GitHub (Jan 4, 2022):
Thanks for the report! It's most probably a logging issue rather than an actual error. We'll fix it in v0.107.3.
@ainar-g commented on GitHub (Jan 17, 2022):
@gspannu, the version
v0.108.0-a.28+008f58c8on theedgerelease channel should contain a fix for this issue. Can you please check if it works for you?@ainar-g commented on GitHub (Jan 20, 2022):
I'll close this issue for now. Please feel free to write if you have any other problems and can't find a solution.