Skip to content
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

Pihole CPU usage on webgui is not the same as inside proxmox/lxc #2324

Closed
JoLong opened this issue Mar 2, 2025 · 3 comments
Closed

Pihole CPU usage on webgui is not the same as inside proxmox/lxc #2324

JoLong opened this issue Mar 2, 2025 · 3 comments

Comments

@JoLong
Copy link

JoLong commented Mar 2, 2025

Versions

Core version is v6.0.4 (Latest: v6.0.4)
Web version is v6.0.1 (Latest: v6.0.1)
FTL version is v6.0.3 (Latest: v6.0.3)

Platform

  • OS and version: Debian 12
  • Platform: LXC Inside Proxmox

Expected behavior

The CPU usare reported by the webgui is correctly displayed

Actual behavior / bug

on a very low utilization from proxmox/htop, pihole reads 30-50%.

Steps to reproduce

Steps to reproduce the behavior:

it's in the webgui, no step to reproduce it, reistalled less than 2 week ago for the v6 update.

Debug Token

Screenshots

Image
Image
Image
Image

Additional context

none atm.

@yubiuser yubiuser transferred this issue from pi-hole/pi-hole Mar 3, 2025
@yubiuser
Copy link
Member

yubiuser commented Mar 3, 2025

Might be fixed by #2297

@DL6ER
Copy link
Member

DL6ER commented Mar 3, 2025

It is a known and long-standing LXC bug that the container gets passed the entire host's load instead of having its own numbers. At the same time, the number of cores is lower, hence, the numbers are off.

I agree that #2297 should fix this.

@DL6ER
Copy link
Member

DL6ER commented Mar 31, 2025

The next version of FTL has been released. Please update and run

pihole checkout master

to get back on-track. The fix/feature branch you switched to will not receive any further updates.

Thanks for helping us to make Pi-hole better for us all!

If you have any issues, please either reopen this ticket or (preferably) create a new ticket describing the issues in further detail and only reference this ticket. This will help us to help you best.

@DL6ER DL6ER closed this as completed Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants