From e16675d08a036ae40bfae311564e01e888b91b71 Mon Sep 17 00:00:00 2001 From: Ainar Garipov Date: Wed, 26 Jan 2022 19:50:49 +0300 Subject: [PATCH] Pull request: FAQ: add info abt plain-text logs Closes AdguardTeam/AdGuardHome#4192. Squashed commit of the following: commit 0956a55240666ab7fa27e7f5af57e6307556550b Author: Ainar Garipov Date: Wed Jan 26 19:26:25 2022 +0300 FAQ: add snap, imp commit ff1b4e883cea4f6e9058123a86f54cffdf7d3e54 Author: Ainar Garipov Date: Wed Jan 26 19:18:38 2022 +0300 FAQ: add info abt plain-text logs --- FAQ.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/FAQ.md b/FAQ.md index 9e9f68b..da30a37 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,6 +1,7 @@ # AdGuard Home - FAQ * [Why AdGuard Home doesn't block ads?](#doesntblock) + * [Where can I inspect the logs?](#logs) * [How to configure AdGuard Home to write verbose-level logs](#verboselog) * [How to show a custom block page](#customblock) * [After installing AdGuard Home, how to change dashboard interface's address?](#webaddr) @@ -71,6 +72,33 @@ ensure that: +## Where can I inspect the logs? + +The default location of the plain-text logs (not to be confused with the query +logs) depends on the operating system and installation mode: + + + + * **OpenWrt Linux:** use the `logread -e AdGuardHome` command. + + * **Linux** systems with **systemd** and other **Unix** systems with + **SysV-style init** including **macOS:** `/var/log/AdGuardHome.err`. + + * **Linux** systems with **Snapcraft** use the `snap logs adguard-home` + command. + + * **FreeBSD** and **OpenBSD:** currently, no logs are written to by default. + That will change in the future, see [issue 4213]. + + * On **Windows:** the [Windows Event Log][wlog] is used. + +[wlog]: https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log +[issue 4213]: https://github.com/AdguardTeam/AdGuardHome/issues/4213 + + + ## How to configure AdGuard Home to write verbose-level logs? To troubleshoot a complicated issue, the verbose-level logging is sometimes