querylog.json no longer being written to after upgrading to 0.97.1 #821

New issue

Closed

opened 2026-03-04 00:50:50 -05:00 by deekerman · 2 comments

deekerman commented

2026-03-04 00:50:50 -05:00

Owner

Originally created by @BlohoJo on GitHub (Jul 19, 2019).

I'm running Windows x64 version of AdGuardHome as a service on Windows 7 SP1.

The log no longer writes to disk (i.e., to data\querylog.json). It appears to only be active in memory. If the service is stopped and restarted, the log is lost.

The querylog.json file is there under AdGuardHome\data, but the modified time stamp is 07/17/2019 12:49 PM, exactly the time that I stopped the service, upgraded to 0.97.1, then restarted the service.

I had upgraded from 0.97, so querylog.json was definitely being written to as of that version. It appears to have broken in 0.97.1.

Originally created by @BlohoJo on GitHub (Jul 19, 2019). I'm running Windows x64 version of AdGuardHome as a service on Windows 7 SP1. The log no longer writes to disk (i.e., to data\querylog.json). It appears to only be active in memory. If the service is stopped and restarted, the log is lost. The querylog.json file is there under AdGuardHome\data, but the modified time stamp is 07/17/2019 12:49 PM, exactly the time that I stopped the service, upgraded to 0.97.1, then restarted the service. I had upgraded from 0.97, so querylog.json was definitely being written to as of that version. It appears to have broken in 0.97.1.

deekerman

2026-03-04 00:50:50 -05:00

closed this issue
added the
wontfix
label

deekerman commented

2026-03-04 00:50:56 -05:00

Author

Owner

@szolin commented on GitHub (Jul 22, 2019):

Can you show application logs? Maybe AGH doesn't have permission to write to querylog.json for some reason.

@szolin commented on GitHub (Jul 22, 2019): Can you show application logs? Maybe AGH doesn't have permission to write to querylog.json for some reason.

deekerman commented

2026-03-04 00:50:58 -05:00

Author

Owner

@stale[bot] commented on GitHub (Sep 20, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 20, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

deekerman referenced this issue

2026-03-04 01:06:04 -05:00

Whitelist & temp disable blocking for unprivileged clients #1146

deekerman referenced this issue

2026-03-04 01:18:01 -05:00

DNS upstream for a specific domain in Client config not working #1437