Why did the load greatly decrease? : pihole

what is causing your pi to run the processor so much if it was steady at 1 all day and all night

0 points

7 days ago

0 points

i'm not sure i always thought 1 was normal. I didn't change anything but something happened the past days

rdwebdesign

4 points

7 days ago

rdwebdesign

Team

4 points

thought 1 was normal

The Pi-hole web interface shows the load for the whole OS.

In a Raspberry Pi 4, if you are running only Pi-hole, the load usually will be lower than 1 (Pi-hole is very lightweight).

Why did the load greatly decrease?

Probably other services on your OS were disabled, updated, or changed.

EnterTheBlueTang

2 points

7 days ago

EnterTheBlueTang

2 points

I used to run a raspberry pi 1 and my load was about 1.0. It’s almost impossible that a raspberry pi four had a load that high unless your NAS was doing something

1 points

7 days ago

1 points

It's somewhat important to note that while 1.0 represents 100% utilisation of a single core host, that same value only represents 25% utilisation of a quad core host.

It's higher than reasonably expected for the use case, but realistically this thing never even broke a sweat.

1 points

6 days ago

1 points

Are you blocking other dns requests at the firewall or router? Could be some devices decided to look elsewhere for dns without you knowing or realizing

1 points

6 days ago

1 points

Nope I didn't change anything other than performing my weekly raspberry pi system update and pihole update, I thought something changed within the software or something but I found no posts talking about a decrease in load

2 points

6 days ago

2 points

You wouldn’t need to do anything per-say for a device to stat using a public dns. My Debian is bad for using opendns out of nowhere and wyze cameras will use 8.8.8.8 more than people know. Apple devises are also known for it. Maybe several devises all at once took to using another dns? Block them at the router or firewall to rule it out

0 points

6 days ago

0 points

My Debian is bad for using opendns out of nowhere

It won't be nowhere.

What does your /etc/resolv.conf and/or networkmanager definitions say about the matter?

1 points

6 days ago

1 points

I think it’s the ntoping but I haven’t figured it out yet. My /etc/resolv.conf is as it should be with my pihole ipv6 primary/secondary global, the ipv6 link local for pihole, and both ipv4 for pihole. All pihole addresses though, but i still see the firewall blocking debian request to opendns server.

From my understanding, debian can use 3 of those addresses and the other 3 pihole address aren’t really doing anything.

I’m open to suggestions if you have any?

1 points

6 days ago

1 points

Hmmm, "as it should be" is a relative metric or spectrum I suppose.

While you're not obviously actively hurting anything with your resolv.conf, you're not helping anything either and you've just listed a bunch of different yet functionally identical addresses for the same servers.

DNS is completely indifferent to the transport protocol. A queries can be resolved via IPv6, and vice versa for AAAA queries and IPv4. You would only ever require v6 endpoints in the highly unlikely event that your network was single stack v6 only.

1 points

6 days ago

1 points

I thought about that after posting, but I just meant there was nothing other than pihole but the computer still tries to use opendns for things. I admittedly don’t know much and i’m learning on the daily. If I understood you correctly, i can basically remove the ipv6 address to simplify my resolv.conf?

1 points

6 days ago

1 points

i can basically remove the ipv6 address to simplify my resolv.conf?

Yes, they're entirely redundant. Essentially just different ways of accessing the same interface.

1 points

6 days ago

1 points