# How to fix unbound.service warnings?

**URL:** <https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711>\
**Category:** Help\
**Created:** [October 1, 2024, 8:46am UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711 "2024-10-01T08:46:32Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sun\_Bear](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/sun_bear/32/43491_2.png) [@Sun\_Bear](https://discourse.pi-hole.net/u/Sun_Bear)\
**Post date:** [October 1, 2024, 8:46am UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/1 "2024-10-01T08:46:32Z")

</div>

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

### Issue

I have installed pi-hole on a dedicated acer atom notebook x64 that is installed with ubuntu 24.04.01 server using command `sudo curl -sSL https://install.pi-hole.net | bash` per [documentation](https://docs.pi-hole.net/main/basic-install/#one-step-automated-install). I have also [installed unbound](https://docs.pi-hole.net/guides/dns/unbound/#setting-up-pi-hole-as-a-recursive-dns-server-solution) and have them both running. However, I noticed 3 warnings in `unbound.service`.

 ![Screenshot from 2024-10-01 16-13-39](https://discourse.pi-hole.net/uploads/default/original/3X/9/5/9531ca986d905cff02b663671d156e84185bb32a.png)

How do I rectify those warnings?

## Expected Behaviour:

No unbound.service warnings.

## Actual Behaviour:

Although `Pihole` and `unbound` are both running (can block ads and function as a recursive DNS), there are still three `unbound.service` warnings that I don't know how to fix.

## Debug Token:

[https://tricorder.pi-hole.net/GcDbA5uy/](https://tricorder.pi-hole.net/GcDbA5uy/)

---

<div class="post-metadata">

**Author:** ![Sun\_Bear](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/sun_bear/32/43491_2.png) [@Sun\_Bear](https://discourse.pi-hole.net/u/Sun_Bear)\
**Post date:** [October 1, 2024, 3:10pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/2 "2024-10-01T15:10:38Z")

</div>

The 2nd warning is due to line 58 of `/etc/unbound/unbound.conf.d/pi-hole.conf`:

```auto
# Ensure kernel buffer is large enough to not lose messages in traffic spikes
so-rcvbuf: 1m

```

I did not understand why the requested resource is not granted given that the system has available RAM.

```auto
master@atom:~$ free
               total used free shared buff/cache available
Mem: 2003824 412480 809088 7512 955628 1591344
Swap: 2097148 0 2097148

```

I came across a similar [question](https://askubuntu.com/q/1285370/541417) posted on AskUbuntu and tried its [answer](https://askubuntu.com/a/1285706/541417) which worked. Below is what I did. The 2nd warning no longer appears.

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/a/6/a67aaa907f0e88f027b89ec5e45f0f6e6bfefe09.png)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [October 1, 2024, 5:15pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/3 "2024-10-01T17:15:48Z")

</div>

As those are _`unbound`_'s warnings (and also, probably specific to your machine/OS), you should consider to consult _`unbound`_'s documentation and support channels.

---

<div class="post-metadata">

**Author:** ![Redback](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/redback/32/31264_2.png) [@Redback](https://discourse.pi-hole.net/u/Redback)\
**Post date:** [October 4, 2024, 6:12am UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/4 "2024-10-04T06:12:48Z")

</div>

> [@Sun\_Bear](#):
>
> /etc/unbound/unbound.conf.d/pi-hole.conf

Had the same problem with the second issue, with subnetcache: prefetch. Disable “prefetch: yes with prefetch: no”, in /etc/unbound/unbound.conf.d/pi-hole.conf, this will solve the issue with cache.

---

<div class="post-metadata">

**Author:** ![stonerl](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/stonerl/32/39097_2.png) [@stonerl](https://discourse.pi-hole.net/u/stonerl)\
**Post date:** [October 5, 2024, 4:38pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/5 "2024-10-05T16:38:07Z")

</div>

> [@Redback](#):
>
> Disable “prefetch: yes with prefetch: no”,

This actually isn't the solution. Turn it back on to `yes`. If you cannot live with the warning, it does no harm, you need to disable the `subnetcache` module, which is enabled by default.

You can check which modules are enabled by executing this:

```sh
$ sudo unbound-control status
version: 1.17.1
verbosity: 0
threads: 2
modules: 3 [subnetcache validator iterator]
uptime: 253177 seconds
options: reuseport control(namedpipe)
unbound (pid 76437) is running...

```

Create a new file :

```sh
sudo touch /etc/unbound/unbound.conf.d/modules.conf

```

and add this content:

```sh
server:
    module-config: "validator iterator"

```

Next, restart unbound:

```sh
sudo systemctl restart unbound.service

```

and confirm that only those two modules are loaded:

```sh
$ sudo unbound-control status
version: 1.17.1
verbosity: 0
threads: 2
modules: 2 [validator iterator]
uptime: 531 seconds
options: reuseport control(namedpipe)
unbound (pid 80384) is running...

```

Now the warning won't show up anymore.

---

<div class="post-metadata">

**Author:** ![Redback](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/redback/32/31264_2.png) [@Redback](https://discourse.pi-hole.net/u/Redback)\
**Post date:** [October 5, 2024, 10:35pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/6 "2024-10-05T22:35:56Z")

</div>

Thanks for the feedback. It works.

---

<div class="post-metadata">

**Author:** ![Sun\_Bear](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/sun_bear/32/43491_2.png) [@Sun\_Bear](https://discourse.pi-hole.net/u/Sun_Bear)\
**Post date:** [October 6, 2024, 11:17am UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/7 "2024-10-06T11:17:02Z")

</div>

> In short, you don't have to do anything for those warnings 🙂

The above is the [answer by @gthess from unbound](https://github.com/NLnetLabs/unbound/issues/1148#issuecomment-2389478070).

---

<div class="post-metadata">

**Author:** ![stonerl](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/stonerl/32/39097_2.png) [@stonerl](https://discourse.pi-hole.net/u/stonerl)\
**Post date:** [October 6, 2024, 11:39am UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/8 "2024-10-06T11:39:54Z")

</div>

Don't forget this part:

> If you don't need subnetcache support you can explicitly set [`module-config: "validator iterator"`](https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html#unbound-conf-module-config)

---

<div class="post-metadata">

**Author:** ![Redback](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/redback/32/31264_2.png) [@Redback](https://discourse.pi-hole.net/u/Redback)\
**Post date:** [October 7, 2024, 4:17pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/9 "2024-10-07T16:17:53Z")

</div>

I have retracted my belief based on the limited information available at the time of my statement. Thank you for providing me with the link. It has greatly assisted me in comprehending errors in general.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [October 28, 2024, 4:18pm UTC](https://discourse.pi-hole.net/t/how-to-fix-unbound-service-warnings/72711/10 "2024-10-28T16:18:43Z")

</div>

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