-
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
BUG - CPU 100% - Randomly #5964
Comments
It seems to be tested and try the fixes on edge versions here #5898 ... |
same issue here, thanks for reporting @Freebase394 |
@locolupo Thank you for your post. |
@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? |
@ainar-g Thanks! Installed Beta version using the folowing command: 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! |
Well... For now everything has been running "quite" stable and solid! My Hypervisor: Proxmox 8.0.3 My VM running: 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) |
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? |
Seems to be fixed. |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found this possible related issue:
Adguard no respond DNS request after certain Time - Docker Contener become Unealthy #5933
Stops responding randomly #5898
DNS requests stop being processed but GUI responsive with high CPU usage. #5962
v0.107.31 stops responding to DNS requests, does not terminate #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:
![image](https://private-user-images.githubusercontent.com/19652056/250825123-ca81c725-c5f5-4222-9d56-5029123932af.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NTYxNzAsIm5iZiI6MTczODk1NTg3MCwicGF0aCI6Ii8xOTY1MjA1Ni8yNTA4MjUxMjMtY2E4MWM3MjUtYzVmNS00MjIyLTlkNTYtNTAyOTEyMzkzMmFmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDE5MTc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE5ODNiM2YxYjRkZjJkNGU4YmJmMGVlNGQ3MzU3YTZjZTk4NDE2ODA5NGRkMmMyZjE4NTU2Yzk1YTAyY2QyZGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.sJAaAIqhhN4EK2Qb6BBKWhOWlhKEPQZyxtXUyEhliFQ)
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:
![image](https://private-user-images.githubusercontent.com/19652056/250823051-ae59f34a-3ecb-477c-8d93-7e0f75151d97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NTYxNzAsIm5iZiI6MTczODk1NTg3MCwicGF0aCI6Ii8xOTY1MjA1Ni8yNTA4MjMwNTEtYWU1OWYzNGEtM2VjYi00NzdjLThkOTMtN2UwZjc1MTUxZDk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDE5MTc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdkZWIwMjBmMGZkMzhhZjAzNWQ0NWQ4Mjc3ZTk1NmZmNTFkYWY2ZWJmZWExMjdiNGMzNmRiZDUwNmY0ZmE4ODYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.O93a9fQV8GYJXfsy51xUPKc6biiRmNra0c_5SuKslgo)
Additional information and/or screenshots
My virtual machine is currently in this state:
![image](https://private-user-images.githubusercontent.com/19652056/250823477-8082ebdf-e10f-4e66-b241-71ad9e19d475.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5NTYxNzAsIm5iZiI6MTczODk1NTg3MCwicGF0aCI6Ii8xOTY1MjA1Ni8yNTA4MjM0NzctODA4MmViZGYtZTEwZi00ZTY2LWIyNDEtNzFhZDllMTlkNDc1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDE5MTc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM1NDc3ODJlOGYwZTAzYzMyMzlhMDQ1YmM2ZDY4ZTFkZmNhMGE0ZTQ3NjkzOGU0NmYxYjdmNTUzYmYxNzk2M2MmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.l42bARZRN7oujQHaEEeuRjG6DZL67kJErTXKC3CPKhs)
CPU consumption status: 100%.
My cluster usualy is at 30ºC || = 86°F on vCore0, and now is like this:
The text was updated successfully, but these errors were encountered: