Pull request: FAQ: add info abt plain-text logs
Closes AdguardTeam/AdGuardHome#4192. Squashed commit of the following: commit 0956a55240666ab7fa27e7f5af57e6307556550b Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Wed Jan 26 19:26:25 2022 +0300 FAQ: add snap, imp commit ff1b4e883cea4f6e9058123a86f54cffdf7d3e54 Author: Ainar Garipov <A.Garipov@AdGuard.COM> Date: Wed Jan 26 19:18:38 2022 +0300 FAQ: add info abt plain-text logs
parent
e3bf36b385
commit
e16675d08a
28
FAQ.md
28
FAQ.md
|
@ -1,6 +1,7 @@
|
||||||
# AdGuard Home - FAQ
|
# AdGuard Home - FAQ
|
||||||
|
|
||||||
* [Why AdGuard Home doesn't block ads?](#doesntblock)
|
* [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 configure AdGuard Home to write verbose-level logs](#verboselog)
|
||||||
* [How to show a custom block page](#customblock)
|
* [How to show a custom block page](#customblock)
|
||||||
* [After installing AdGuard Home, how to change dashboard interface's address?](#webaddr)
|
* [After installing AdGuard Home, how to change dashboard interface's address?](#webaddr)
|
||||||
|
@ -71,6 +72,33 @@ ensure that:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
## <a href="#logs" id="logs" name="logs">Where can I inspect the logs?</a>
|
||||||
|
|
||||||
|
The default location of the plain-text logs (not to be confused with the query
|
||||||
|
logs) depends on the operating system and installation mode:
|
||||||
|
|
||||||
|
<!--
|
||||||
|
TODO(a.garipov): Add more info about Docker; add links to tools.
|
||||||
|
-->
|
||||||
|
|
||||||
|
* **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
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## <a href="#verboselog" id="verboselog" name="verboselog">How to configure AdGuard Home to write verbose-level logs?</a>
|
## <a href="#verboselog" id="verboselog" name="verboselog">How to configure AdGuard Home to write verbose-level logs?</a>
|
||||||
|
|
||||||
To troubleshoot a complicated issue, the verbose-level logging is sometimes
|
To troubleshoot a complicated issue, the verbose-level logging is sometimes
|
||||||
|
|
Loading…
Reference in New Issue