Avoiding AdGuardHome log spam when network is down

I have an AdGuardHome installation (via apk) and I'm quite happy with it, but when internet connectivity is down, AGH fills the log with so many messages that it's impossible to see anything else (in particular, what caused the connectivity issue...)

Tue Mar 10 12:25:36 2026 user.notice AdGuardHome[1]: 2026/03/10 12:25:36.966782 [error] dnsproxy: handling request proto=tcp err="using request handler: dialing 8.8.8.8:53 over udp: dial udp 8.8.8.8:53: connect: network is unreachable\ndialing 1.1.1.1:53 over udp: dial udp 1.1.1.1:53: connect: network is unreachable\ndialing 1.0.0.1:53 over udp: dial udp 1.0.0.1:53: connect: network is unreachable\ndialing 8.8.4.4:53 over udp: dial udp 8.8.4.4:53: connect: network is unreachable"

I guess logging can be disabled altogether, but I'd like to have sane, non-spammy, logs.
Any suggestions?

https://openwrt.org/releases/25.12/notes-25.12.0#upgrading_to_2512 ?

Thank you for the quick reply, but what's the relevance of this?

  1. release notes say nothing about AGH;
  2. the problem has existed before 25.12;
  3. I've been running snapshot since 2023.

Add -l /dev/null to agh command line.

  1. No, but logging in general.
  2. Sorry, crystal ball was offline, I couldn't see this.
  3. -||-

The proper way to disabling AGH logging completely is via /etc/adguardhome.yml, but I was asking for an option to reduce specific messages in a specific scenario, not for a kill-switch.

Hopefully someone more familiar with how AGH works could respond.
Perhaps @mercygroundabyss or @krazeh? couldn't find maintainer nicks on the forum.

It is unhandled error in golang, so you are in an all or nothing situation.
This is not configurable.

Thanks, I'll post this over AGH's GH.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.