-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
Massive CPU usage of FTL since update to v6 #2199
Comments
pi-hole/pi-hole#5894 (comment) this help by chance? |
Sorry for picking the wrong repo and thanks for moving the issue @yubiuser.
Not really, I mean, because they're empty, it does actually get the chance to load the query graphs faster in the Webinterface. (edits: typos, formatting and clarification) |
No problem. It's difficult for users to know which of our repos fits best. |
Could you check if your database is okay? What is the output of
|
This issue has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/web-interface-slow-after-update-from-5-to-6/76280/17 |
Again, I get resolve error, just like shown above, when I tried to get the debug token.
|
What resolver is set in |
Sorry, I ran out out of patience troubleshooting a nearly unresponsive system. I reflashed the whole system. |
This would be unusual, to have a local instance of unbound specified as an upstream DNS server in /etc/resolv.conf. Note that this is different than the upstream DNS server used by Pi-hole. /etc/resolv.conf is the DNS server used by the host OS. |
Versions
pihole -v
Platform
OS and version
cat /etc/os-release
Platform
Raspberry Pi 2B
Expected behavior
Using 60% CPU at max (with idling websession) - like before the upgrade
Actual behavior / bug
pihole-FTL 95% CPU usage on average constantly (even without a websession)
Steps to reproduce
Steps to reproduce the behavior:
Debug Token
pihole -d
Screenshots
Additional context
Unbound running, but doesn't seem to work anymore, but wasn't able to troubleshoot, because system is completely unresponsive.
Set 8.8.8.8 for DNS on router temporarily, because pihole DNS did not respond anymore.
The text was updated successfully, but these errors were encountered: