Skip to content
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

Don't block DNS, DHCP and WebUI loading with query log parsing #784

Closed
ilya-fedin opened this issue May 31, 2019 · 1 comment
Closed

Don't block DNS, DHCP and WebUI loading with query log parsing #784

ilya-fedin opened this issue May 31, 2019 · 1 comment

Comments

@ilya-fedin
Copy link

Steps to reproduce

  1. Buy Irbis A or other device with Alisa (or make a lot of requests)
  2. If block telemtry (which in default lists so), it will generate ~100-200K requests in 24 hours
  3. In 24 hours log will have size of ~96MB
  4. Adguard will start very long (at least on HDD)

Expected behavior

DNS, DHCP and WebUI start immediately, query log parsing in other thread

Actual behavior

DNS, DHCP and WebUI waits query log parsing to be end, as result, some services may working incorrectly without DNS on start (and it happens)

Your environment

Raspberry Pi 2 with Raspbian Stretch and HDD connected over USB as root

Description Value
Version of AdGuard Home server: v0.95-hotfix
How did you setup DNS configuration: Router
If it's a router or IoT, please write device model: Raspberry Pi 2
Operating system and version: Raspbian Stretch
@szolin
Copy link
Contributor

szolin commented Dec 11, 2019

Query logs access is now dynamic - it doesn't interfere with startup.

@szolin szolin closed this as completed Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants