Failing to install unbound

Help
1

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

I am currently trying to install unbound with the package manager on my rasperry pi using the guide from unbound - Pi-hole documentation but i always get this error message instead also seems that it partially did install because it began messing with the 53 port causing ftl to not be able to properly hook up with it.

Expected Behaviour:

rasperry pi 4 for ubuntu 22.04.1 LTS unbount installing without issue then going to the next setup steps to set it up properly-

Actual Behaviour:

Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xeu unbound.service" for details.
invoke-rc.d: initscript unbound, action "restart" failed.
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2022-09-01 14:21:32 CEST; 43ms ago
Docs: man:unbound(8)
Process: 1521 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
Process: 1524 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
Process: 1527 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
Process: 1528 ExecStopPost=/usr/lib/unbound/package-helper chroot_teardown (code=exited, status=0/SUCCESS)
Main PID: 1527 (code=exited, status=1/FAILURE)
CPU: 75ms

Debug Token:

[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]

2

i am aware this is probably not really an issue with pihole itself but thats the issue

3

Please post the output of the following command from the Pi terminal:

sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*

4

/etc/unbound/unbound.conf:include-toplevel: "/etc/unbound/unbound.conf.d/*.conf" /etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:server: /etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf: auto-trust-anchor-file: "/var/lib/unbound/root.key"

5

I woukd like to add, when I had these issues (40 posts thread full of similar errors) I started over and properly followed the instructions, it works great.

Moreover, Unbound (when I read the guide anyway a couple months ago or so) uses port 5335, and does not seem to use port 53 for the program itself.

Could this be the issue? I had the same error message for unbound, telling me to see the journal. When I followed the guide inside a Debian VM, zero issues. I guess that's not saying much because for some reason, so many others have so many different issues.

I figured, with all the initial errors that I caused--if I could follow to guide and get it right, just about everyone should have a similar experience too.

6

strangly enough the unbound installation seems to work ? after manually writing the config file and then using sudo service unbound restart dig pi-hole.net @127.0.0.1 -p 5335 to test even trough the error is there it seems to work is this fine or is there another undlying issue here?

7

If this is the entire output, you are missing an entire file - the configuration file provided by our guide.

9

I wrote the file manually in with nano so it should be fine right?

10

It should be, but it isn't showing up in your configuration folder. The command I provided shows all non-commented lines in every .conf file in the /etc/unbound directory.

sudo nano /etc/unbound/unbound.conf.d/pi-hole.conf

Paste the contents of the configuration provided in our guide, save and exit.

sudo service unbound restart

11

/etc/unbound/unbound.conf:include-toplevel: "/etc/unbound/unbound.conf.d/*.conf" /etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:server: /etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf: auto-trust-anchor-file: "/var/lib/unbound/root.key" /etc/unbound/unbound.conf.d/pi-hole.conf:server: /etc/unbound/unbound.conf.d/pi-hole.conf: verbosity: 0 /etc/unbound/unbound.conf.d/pi-hole.conf: interface: 127.0.0.1 /etc/unbound/unbound.conf.d/pi-hole.conf: port: 5335 /etc/unbound/unbound.conf.d/pi-hole.conf: do-ip4: yes /etc/unbound/unbound.conf.d/pi-hole.conf: do-udp: yes /etc/unbound/unbound.conf.d/pi-hole.conf: do-tcp: yes /etc/unbound/unbound.conf.d/pi-hole.conf: do-ip6: no /etc/unbound/unbound.conf.d/pi-hole.conf: prefer-ip6: no /etc/unbound/unbound.conf.d/pi-hole.conf: harden-glue: yes /etc/unbound/unbound.conf.d/pi-hole.conf: harden-dnssec-stripped: yes /etc/unbound/unbound.conf.d/pi-hole.conf: use-caps-for-id: no /etc/unbound/unbound.conf.d/pi-hole.conf: edns-buffer-size: 1232 /etc/unbound/unbound.conf.d/pi-hole.conf: prefetch: yes /etc/unbound/unbound.conf.d/pi-hole.conf: num-threads: 1 /etc/unbound/unbound.conf.d/pi-hole.conf: so-rcvbuf: 1m /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 192.168.0.0/16 /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 169.254.0.0/16 /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 172.16.0.0/12 /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 10.0.0.0/8 /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: fd00::/8 /etc/unbound/unbound.conf.d/pi-hole.conf: private-address: fe80::/10
Seems like that did it yeah i tried the command again and it shows up now unbount also responds like its supposed to when i run it trough the test commands in the guide

12

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