mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
BUG - CPU 100% - Randomly #4566
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#4566
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Freebase394 on GitHub (Jul 4, 2023).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found this possible related issue:
#5933
#5898
#5962
#5896
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/AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
AdGuard Home, version v0.107.33
Action
RESUSULT:
adguard02:/opt/AdGuardHome# nslookup -debug -type=a 'www.google.com' '127.0.0.1'
Server: 127.0.0.1
Address: 127.0.0.1:53
Query #0 completed in 35ms:
Non-authoritative answer:
Name: www.google.com
Address: 216.239.38.120
Expected result
I expected the AdGuardHome process to run stably and normally!
Actual result
But it turns out that somehow, it has some entropy and is being used abruptly consuming all system CPU resources.
WARNING: This is my 3rd attempt, I had AdGuardHome running on my RaspberyPi3 b+, I had the version "AdGuard Home v0.107.28xx" on it and it ran smoothly and beautifully, I even had my raspbery pi on for weeks straight, no anomalies.
But from some of the versions "AdGuard Home v0.107.30xx" totally randomly, and without explanation my raspbery pi simply crashed and stopped responding[From the looks of it, it seemed to be stuck somehow, as the system was totally down because it was completely in use (all its cores being in use randomly at 100%)] I tried to reinstall multiple times, but always the same, "A few hours later, the same thing"
Since a few days ago I switched to a x64 environment "Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz".
Note: I can guarantee this single vCore is as strong or even stronger than the 4 cores of my raspberryPi 3 b+.
I've enabling the following features on the new AdGuardHome machine:
1 vCore - Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
4096 Mb(4GB) RAM
"AlpineOS --> 3.18.0"
I can prove that the maximum CPU consumptions when updating BlockLists etc... It just represents this:
This always responding and processing to more and 10 clients in house....
Suddenly and out of nowhere, something happens: I don't understand where the anomaly comes from:
Additional information and/or screenshots
My virtual machine is currently in this state:
CPU consumption status: 100%.
My cluster usualy is at 30ºC || = 86°F on vCore0, and now is like this:
@Freebase394 commented on GitHub (Jul 6, 2023):
It seems to be tested and try the fixes on edge versions here #5898 ...
Later, if fixed we can close this issue ...
@locolupo commented on GitHub (Jul 10, 2023):
same issue here, thanks for reporting @Freebase394
@Freebase394 commented on GitHub (Jul 11, 2023):
@locolupo Thank you for your post.
This proves that I am not the only human being having this problem.
Could you please post some Prints of the anomalies of your problem, like cpu status.... machine with 100% usage... print of the crash of your virtual machine etc... logs etc...please
@ainar-g commented on GitHub (Jul 11, 2023):
@Freebase394, @locolupo, #5896 is the issue where we're tracking this. As the fix developed there has been ported to Edge and Beta channels, could any one of you check if it works for you?
@Freebase394 commented on GitHub (Jul 11, 2023):
@ainar-g Thanks! Installed Beta version using the folowing command:
Script to install a beta version:
curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c beta
I'm going to leave this server running, it's being the primary DNS for my entire home network, with 7~10 devices around here on the network!
Let's see how the one behaves!
Hopefully well!
I promise to bring new feedback in a few days!
My VM properties:
For Beta installed just now:
All ok for now:
Version installed:
@Freebase394 commented on GitHub (Jul 12, 2023):
Well...
@ainar-g This is for you and your team to see that the work you have done so far is working very well!
For now everything has been running "quite" stable and solid!
Now i'm using a total of rules equal to: (+/-) 6365523 on my own AdGuardHome [DNS blocklists AdGuard Home will block domains matching the blocklists]
My Hypervisor: Proxmox 8.0.3
CPU: i5-3470 CPU @ 3.20GHz (4 total cores)
My VM running:
Status: running
HA State: none
Node: pve
CPU usage: 0.04% of 2 CPU(s) (I'm only have 2 vCPU)
Memory usage: 32.00% (511.96 MiB of 1.56 GiB)
SWAP usage: 2.50% (9.99 MiB of 400.00 MiB)
Bootdisk size: 3.02% (240.61 MiB of 7.78 GiB)
Every time I update my lists, this is the status of the VM behavior on top of an LX container(Alpine OS Linux --> Very small distro)
It does not reach values above 30%/45% of the entire cpu!
Memory Consuption:
Network status:
Disk IO
@ainar-g commented on GitHub (Jul 12, 2023):
Short-term CPU spikes during filter updates are to be expected, especially if there are a lot of rules. I assume, as long as the persistent 100 % CPU spike is gone, the issue can be be considered resolved by the update?
@Freebase394 commented on GitHub (Jul 18, 2023):
Seems to be fixed.
"AdGuard Home, version v0.108.0-b.41"
All ok after 5 days running!
I will close this issue now!