-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging no longer working #6372
Comments
I'm not sure what you mean here. The query log retains one additional file, meaning that if the rotation interval is set to 7 days, you'll have about 14 days of query logs, which seems to be precisely what you're observing? |
Ah, I see, thanks. What are the settings in the querylog:
ignored: []
interval: 2160h
size_memory: 1000
enabled: true
file_enabled: true Also, do you see any querylog-related errors in the verbose log? |
Thank you for your help |
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, ARM64
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.40
Action
Reviewing logs within query log has stopped updating since October 14th. Tested domains what are on allow and block lists.
Reviewed settings confirming logging is still enabled and log rotation is set to 7 days
Checked/confirmed AdGuard is up to date
Updated/rebooted hostOS
Expected result
DNS requests recorded within logs, highlighting blocked and allowed domains
Logs being rotated
Actual result
Domains correctly blocked/allowed but upon reviewing logs, no records of DNS requests
Log rotation not working past 7 days
Graph stats appear to be updating as expected
Additional information and/or screenshots
Install Raspberry Pi 3B on Raspbian
The text was updated successfully, but these errors were encountered: