i/o timeout

[AndyLin2020]

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, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.55

Action

AdGuardHome监听53端口，127.0.0.1:5335为上游DNS服务器Mosdns，功能都正常，最近AdguardHome一直都会出现以下错误日志，基本上三分钟出现一次，不知道问题在哪里？之前版本好像没这问题。

AdGuardHome is listening on port 53, using 127.0.0.1:5335 (Mosdns) as the upstream DNS server. All functions appear normal, but recently AdGuardHome has been consistently logging the following error, approximately every three minutes. I'm unsure of the source of the problem. Previous versions didn't seem to have this issue.

Expected result

Hoping this issue can be fixed.

Actual result

2025/01/19 17:01:54.846952 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:17257->127.0.0.1:5335: i/o timeout"
2025/01/19 17:01:59.927083 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:9676->127.0.0.1:5335: i/o timeout"
2025/01/19 17:04:55.936911 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:46244->127.0.0.1:5335: i/o timeout"
2025/01/19 17:05:01.007897 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:39178->127.0.0.1:5335: i/o timeout"
2025/01/19 17:07:57.061010 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:30837->127.0.0.1:5335: i/o timeout"
2025/01/19 17:08:02.140304 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:47019->127.0.0.1:5335: i/o timeout"
2025/01/19 17:10:58.190939 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:2341->127.0.0.1:5335: i/o timeout"
2025/01/19 17:11:03.266110 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:33915->127.0.0.1:5335: i/o timeout"
2025/01/19 17:13:59.263049 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:50627->127.0.0.1:5335: i/o timeout"
2025/01/19 17:14:04.333597 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:58480->127.0.0.1:5335: i/o timeout"
2025/01/19 17:17:00.366763 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:50515->127.0.0.1:5335: i/o timeout"
2025/01/19 17:17:05.446045 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:40976->127.0.0.1:5335: i/o timeout"
2025/01/19 17:20:01.466692 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:36661->127.0.0.1:5335: i/o timeout"
2025/01/19 17:20:06.540906 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:62275->127.0.0.1:5335: i/o timeout"
2025/01/19 17:23:02.557808 ERROR response received addr=127.0.0.1:5335 proto=udp status="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:42337->127.0.0.1:5335: i/o timeout"

Additional information and/or screenshots

No response

[tjharman]

Those logs indicate to me that Adguard is having trouble talking to Mosdns.

That would, with the logs you've presented, appear to be a Mosdns issue?

What specifically makes you think this is an AdguardHome issue - and can you clarify if it's actually stopping AGH from working?

[AndyLin2020]

Those logs indicate to me that Adguard is having trouble talking to Mosdns.

That would, with the logs you've presented, appear to be a Mosdns issue?

What specifically makes you think this is an AdguardHome issue - and can you clarify if it's actually stopping AGH from working?

Communication between AdGuardHome and Mosdns is fine. works perfectly. The only issue is the recurring error log in AdGuardHome, which appears every three minutes like clockwork. This is what I find strange. It doesn't seem to actually affect AdGuardHome's functionality, but the consistent logging is concerning.