accepting quic stream: Application error 0x376 (remote): reconnect #6425
Comments
|
This could be the same issue as #6422. Can you please try adding Also, quic-go has been updated to a newer version in the Edge channel, so can you also check if the issue persist there without the env. variable? |
|
tested with the env var, seems that part of the problem persists. |
|
tested in version v0.108.0-b.49, problem still there |
|
I'm not sure what caused AGH to terminate in the first place, since such application errors shouldn't cause it to panic. We also cannot reproduce this on any of our machines, and there doesn't seem to be any mention of error code Some additional pieces of data that should clarify things:
|
|
the quic/h3 upstreams used: removed these upstreams, and set hope these info can help. |
|
Right, I was thinking that maybe it's related to another quic-go issue, but it probably isn't. Are there many clients using DoQ? Have you noticed any correlations between a particular client and the occurrence of these errors? A misbehaving DNS client on one or a few of them perhaps? |
|
around 2-3 clients using doq, not many queries per second. I did try making queries to see correlations, but didn't observe any. so I guess .. just wait for possible other cases then |
ainar-g
changed the title
|
didn't pay much attention to DNSs for a while, and somehow this issue disappeared after several updates. so i closed it |
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.41
Action
tail /$agh_logs/stderr.log
Expected result
normal output
Actual result
2023/11/15 14:48:10.252986 [error] accepting quic stream: Application error 0x376 (remote): reconnect
2023/11/15 14:48:11.037386 [error] accepting quic stream: APPLICATION_ERROR (remote)
2023/11/15 14:48:11.123583 [error] accepting quic stream: Application error 0x1 (remote)
2023/11/15 14:48:11.259371 [error] accepting quic stream: Application error 0x1 (remote)
2023/11/15 14:48:21.806773 [error] accepting quic stream: Application error 0x376 (remote): reconnect
2023/11/15 14:48:22.204339 [error] accepting quic stream: Application error 0x376 (remote): reconnect
2023/11/15 14:48:52.267501 [info] Received signal "terminated"
2023/11/15 14:48:52.267538 [info] stopping AdGuard Home
2023/11/15 14:48:52.267543 [info] stopping http server...
2023/11/15 14:48:52.267655 [info] stopped http server
2023/11/15 14:48:52.267686 [info] dnsproxy: stopping dns proxy server
2023/11/15 14:48:52.268049 [info] udpListen.ReadFrom() returned because we're reading from a closed connection, exiting loop
2023/11/15 14:48:52.268080 [info] udpListen.ReadFrom() returned because we're reading from a closed connection, exiting loop
2023/11/15 14:49:22.490093 [info] AdGuard Home, version v0.107.41
2023/11/15 14:49:22.493384 [info] tls: using default ciphers
2023/11/15 14:49:22.495800 [info] safesearch default: disabled
Additional information and/or screenshots
as the log indicates, the agh core keeps terminating and restarting for every ~2 minutes.
during its termination
'lsof -i :53'shows that port 53 is not bound.wondering what Application error 0x376 and 0x1 is, and what it has to do with accepting quic.
(BTW my clients do use quic:// and h3:// when querying agh)
The text was updated successfully, but these errors were encountered: