Need confirnmation

Please follow the below template, it will help us to help you!

Hello, this is my first time using Pi-Hole. I've heard about PiHole in the past and this is my first time looking into it. I recently got a Synology Nas for storage reasons and saw that it can do Container Manager which I then learned PiHole can be downloaded to. I see it's working as intended but this error message keeps popping up
" Long-term load (15min avg) larger than number of processors: 4.2 > 4
This may slow down DNS resolution and can cause bottlenecks."

I'm suspecting its got to do with resources getting exhausted but nothing seems to be spiking or maxing out in the resource manager in Synology. I was wondering if the debug token would tell what resources are maxing out on or what else could be causing the bottlenecks. Thanks

Expected Behaviour:

Error message not popping up

Actual Behaviour:

Error message keeps popping up

Debug Token:

[✓] Your debug token is: https://tricorder.pi-hole.net/GTKj2S27/

If you're not seeing any performance issues you can ignore or disable the load check.

The load check can be useful for a standalone install, such as on a Raspberry Pi, since the load seen represents resource that could impact Pi-hole. In the case of the container, it has its allocated resource but shares the kernel with the rest of the NAS and sees and reports the load caused by all the other NAS processes outside of Pi-hole's container, which are being managed by DSM (Synology's OS). So in a sense it's a "false alarm".

Your debug log looks okay but note that your router's DHCP is handing out both Pi-hole's IP and your ISP's DNS server. This means that clients will use both and will therefore sometimes bypass Pi-hole. To fix this, go into your router and ensure that in the LAN DHCP section only the Pi-hole IP is being given out. Hopefully the router will let you make that change. Then take your devices off and back on the network to pick up the changed settings.

Received 301 bytes from eth0:192.168.40.1
...
      dns-server: 192.168.40.198
      dns-server: xx.xx.xx.xx (your ISP's DNS, remove this)
      router: 192.168.40.1
1 Like

No.

The debug log only reports the Long-term load (15min avg), not the cause of this load. To find out what is causing this high load, you will need to use top, htop, atop or a similar program to investigate.

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.