-
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
Filter directory filling up with old filter files #3567
Comments
Hello and thank you for your report. We can't seem to reproduce this issue on our machines. There are filter backup files, but they all must have a |
Here's the state of the directory one day later:
These are the two blocklists I have installed, and it seems it's the first file that's causing problems somehow. https://blocklistproject.github.io/Lists/porn.txt FWIW I'm now running v0.107.0-a.157+80548233 |
As of now the issue has partly resolved itself. The directory is no longer filling up with temporary files. The problem is now limited to when I trigger a manual update only. I get this error in the Web UI:
And a temporary file is created and not deleted in the filter folder:
I'm now running v0.107.0-a.161+fac574d3 |
Thanks for the info, we seem to have found the root cause of the issue and are working on fixing it. |
Merge in DNS/adguard-home from 3567-old-filters to master Updates #3567. Squashed commit of the following: commit d5cc419 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 19:22:49 2021 +0300 home: lock doc commit 54edba6 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 14:16:20 2021 +0300 home: imp code, docs commit e6dde1d Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 13:53:50 2021 +0300 home: imp code, logic commit b258b62 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Sep 14 19:35:14 2021 +0300 all: imp log of changes commit 9b66cde Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Sep 14 18:56:52 2021 +0300 home: imp filter upd
@gabrielwhite, we've just pushed the latest build to the edge channel. It should fix some logic problems related to the issue. Could you please check, if it works with your filter lists? |
Upon upgrading, I ran into the same issue again. Additionally it seemed that Adguard crashed and restarted after triggering a manual update. I'm running v0.107.0-a.166+176a344a. Once it started crashing I thought it may have been a memory issue, so I increased the memory limitation on the docker to 320MB (it had been capped at 256MB), and this stopped the issue. I'd previously moved to using the edge version because it ran without crashing in 256MB (0.106 wouldn't run with less memory). Adguard had been causing crashes on the OrangePi because it was chewing up too much memory. |
Well, could you please help us to troubleshoot this issue. We need you to configure Home to collect verbose log into a file. Note that in case of Docker's container the path to log file points to the container's filesystem, so the simplest way is a file in working or configuration directory which are mounted. Then trigger the manual filter update and post the file here or send it to devteam@adguard.com with the issue number. |
@ainar-g It seems to when you take the action
Since the user do the such things which most often means that they don't need those blocklist, if the user want to temporary pause it, they should temporary not enable the blocklist to instead of deleting it. If it is possible not to rename the deleted blocklist but delete the blocklist file when you take the action BTW I used the https://blocklistproject.github.io/Lists/porn.txt filter for the example. |
@gabrielwhite, we've received your logs, thanks! We'll inspect them as soon as possible. |
@gabrielwhite, we've reproduced the issue and got same results. I'm afraid the amount of RAM allocated for the container is the main cause of these crashes and unremoved temporary files. We've performed a couple of memory tests and concluded that 512 should be enough to handle updating of lists with around 3 million rules. However, you may try to decrease the limitation to some sensible minimum, because it's the only parameter for now which directly affects AdGuard Home stability with regards to updating filters. We'll close the issue for now, since we cannot do anything about unrecoverable crashes for the moment. We'll consider further optimizations. |
Merge in DNS/adguard-home from 3567-old-filters to master Updates AdguardTeam#3567. Squashed commit of the following: commit d5cc419 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 19:22:49 2021 +0300 home: lock doc commit 54edba6 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 14:16:20 2021 +0300 home: imp code, docs commit e6dde1d Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Wed Sep 15 13:53:50 2021 +0300 home: imp code, logic commit b258b62 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Sep 14 19:35:14 2021 +0300 all: imp log of changes commit 9b66cde Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Tue Sep 14 18:56:52 2021 +0300 home: imp filter upd
Issue Details
Expected Behavior
That old filter files are deleted automatically
Actual Behavior
I got a "disk full" warning from my OrangePi One Plus and found that the filters directory had 22GB of files in it across more than 100 files in dockers/adguardhome/data/work/data/filters
I have 2 filters enabled, which total around 60MB.
I deleted all the files in the directory, reinstalled the filters. This issue is likely accumulated over time earlier than the current version as there were many files dating back at least weeks.
Subsequently when I check for updates one of the filters generates an error shown in a red toast:
Error: control/filtering/refresh | <html> ,<head><title>502 Bad Gateway</title></head>, ,<body> ,<center><h1>502 Bad Gateway</h1></center>, ,<hr />,<center>openresty</center>, </body>, </html> | 502
This error doesn't show on the other adguard server I use with the same configuration, but running v0.106.3.
When I look in the filter directory I see a new file created without a "txt" extension.
The text was updated successfully, but these errors were encountered: