After trying to enable HaGeZi's Threat Intelligence Feeds to Blocklist. It cause AdGuard Home not working on SparkBox unless if I manually disable or remove it in AdGuardHome.yaml file by using Terminal through SSL. HaGeZi's Threat Intelligence Feeds
7 replies
Chris wrote:
Thanks for the detailed report, and sorry AdGuard was down for your whole network while this happened. Leaving that list off while we confirm the cause is the safe choice. What I think is happening (a hypothesis until we see one line from your box): AdGuard runs on SparkBox with a 256 MB memory cap, and a large blocklist can need more memory than that to load. When it goes over, the system stops the container and Docker restarts it, which matches the crash loop you describe. One read-only check will confirm it. In the SparkBox terminal, run: sudo docker inspect sb-adguard --format 'OOMKilled={{.State.OOMKilled}} Restarts={{.RestartCount}}' If it prints OOMKilled=true, that confirms it. Reply with just that line. Please don't paste the full log, since it can include addresses and device names. I've logged your report for the team with these details.
ABOhiccups wrote:
Will there be a feature to increase memory cap on certain Docker App?
Chris wrote:
Yes, you can already raise it yourself. In the dashboard go to Settings, then Server Config, then Resource Limits (per app). AdGuard Home has its own row with a RAM field, and a value you save there survives updates. Saving recreates AdGuard, so DNS on your network drops for a moment. It needs an activated licence. Please run the read-only check first, so we only raise the limit if it is the cause. In the SparkBox terminal, run: sudo docker inspect sb-adguard --format 'OOMKilled={{.State.OOMKilled}} Restarts={{.RestartCount}}' Reply with that one line. If it prints OOMKilled=true, raising the AdGuard RAM limit is the next step. If it prints false, the cause is somewhere else and we will look again. If you don't see that section, reply with your SparkBox version and we will check. I have also logged your question for the team.
ABOhiccups wrote:
The section you've mentioned in Settings Server Config is not in V3 Dashboard. It's only in V1 Classic Dashboard.
Chris wrote:
You're right, and I'm sorry. My last reply gave you the wrong place to look. Resource Limits (per app) is not on the V3 Server Config page. It only exists in the Classic dashboard, where the RAM box for AdGuard Home is. To reach it from V3: open Settings, then Server Config, then Media folders, and press Open media settings. That opens Classic's Server Config page, and Resource Limits (per app) is there with a RAM field for AdGuard Home. Saving a value needs an activated licence, and it recreates AdGuard, so DNS drops for a moment. I have corrected what I know about where this setting is, so it doesn't happen to the next person. Please don't change the limit yet. The check still comes first. In the SparkBox terminal, run: sudo docker inspect sb-adguard --format 'OOMKilled={{.State.OOMKilled}} Restarts={{.RestartCount}}' Reply with just that line. If it prints OOMKilled=true, the memory cap is the cause and the RAM field above is the fix. If it prints false, we will look at the cause another way.
ABOhiccups wrote:
I've tried to change RAM cap in Server Config (V1 Classic Dashobard). It gives me an error. EACCES: permission denied, open '/app/state/overrides/adguard.yml.tmp.1.db321357'
Chris wrote:
Sorry. I told you to use that RAM field before I knew the save would work on your box, and it doesn't. When you press save, the dashboard tries to write the new limit into a settings folder inside your SparkBox install. On your box the dashboard is not allowed to write there, so the save stops before anything changes and your AdGuard setting is the same as before. I've logged this for the team with the details, and I've noted that this save can fail on some installs so the next person is checked before being sent there. One read-only check first. In the SparkBox terminal, run: ls -ld /opt/sparkbox/state/overrides If SparkBox is installed somewhere other than /opt/sparkbox, use that folder instead. Reply with the one line it prints. Please leave the RAM value alone and don't change any permissions yourself until we know which folder is the problem. The OOMKilled check from earlier is still the one that decides whether the memory limit is the real fix, and we'll ask for it once the save works.