Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


MikeAqua

8024 posts

Uber Geek
+1 received by user: 3817


#320313 30-Jul-2025 21:38
Send private message

I followed the instructions on the Pi-Hole site for installing unbound.  This included creating the config file.

 

Install seemed to go fine.  I ran the unbound error check and got the following results:

 

 

 

unbound-checkconf: no errors in /etc/unbound/unbound.conf.d/pi-hole.conf 

 

 

 

All good.  I restarted UnBound and got this error message:

 

 

 

 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.

 

 

 

I inspected those logs and the results are posted below. I'd appreciate any advice on what might be wrong.

 

 

 

 Loaded: loaded (/lib/systemd/system/unbound.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-07-30 21:21:48 NZST; 1min 20s ago
       Docs: man:unbound(8)
    Process: 66812 ExecStartPre=/usr/libexec/unbound-helper chroot_setup (code=exited, status=1/FAILURE)
    Process: 66814 ExecStartPre=/usr/libexec/unbound-helper root_trust_anchor_update (code=exited, status=1/FAILURE)
    Process: 66816 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
    Process: 66817 ExecStopPost=/usr/libexec/unbound-helper chroot_teardown (code=exited, status=1/FAILURE)
   Main PID: 66816 (code=exited, status=1/FAILURE)
        CPU: 69ms
 

 

 

 

 

 

 

 

 

 

Jul 30 21:43:51 PiHole systemd[1]: Stopped unbound.service - Unbound DNS ser>
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 17970 and the job result is done.
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Start request repeated t>
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Failed with result 'exit>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-co>
Jul 30 21:43:51 SPIHole systemd[1]: Failed to start unbound.service - Unbound>
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 17970 and the job result is failed.
lines 3297-3319/3319 (END)
Jul 30 21:43:51 PiHole systemd[1]: Stopped unbound.service - Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 17970 and the job result is done.
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Start request repeated too quickly.
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Jul 30 21:43:51 PiHole systemd[1]: Failed to start unbound.service - Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 17970 and the job result is failed.
lines 3297-3319/3319 (END)
Jul 30 21:43:51 PiHole systemd[1]: Stopped unbound.service - Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 17970 and the job result is done.
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Start request repeated too quickly.
Jul 30 21:43:51 PiHole systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Jul 30 21:43:51 PiHole systemd[1]: Failed to start unbound.service - Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 17970 and the job result is failed.

 

 

 

 

 

 





Mike


Create new topic
MikeAqua

8024 posts

Uber Geek
+1 received by user: 3817


  #3398561 30-Jul-2025 22:59
Send private message

Here are the settings from the config file (comments removed)

 

/etc/unbound/unbound.conf/pi-hole.conf:server:
/etc/unbound/unbound.conf/pi-hole.conf:    verbosity: 0
/etc/unbound/unbound.conf/pi-hole.conf:    interface: 127.0.0.1
/etc/unbound/unbound.conf/pi-hole.conf:    port: 5335
/etc/unbound/unbound.conf/pi-hole.conf:    do-ip4: yes
/etc/unbound/unbound.conf/pi-hole.conf:    do-udp: yes
/etc/unbound/unbound.conf/pi-hole.conf:    do-tcp: yes
/etc/unbound/unbound.conf/pi-hole.conf:    do-ip6: no
/etc/unbound/unbound.conf/pi-hole.conf:    prefer-ip6: no
/etc/unbound/unbound.conf/pi-hole.conf:    harden-glue: yes
/etc/unbound/unbound.conf/pi-hole.conf:    harden-dnssec-stripped: yes
/etc/unbound/unbound.conf/pi-hole.conf:    use-caps-for-id: no
/etc/unbound/unbound.conf/pi-hole.conf:    edns-buffer-size: 1232
/etc/unbound/unbound.conf/pi-hole.conf:    prefetch: yes
/etc/unbound/unbound.conf/pi-hole.conf:    num-threads: 1
/etc/unbound/unbound.conf/pi-hole.conf:    so-rcvbuf: 1m
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 192.168.0.0/16
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 169.254.0.0/16
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 172.16.0.0/12
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 10.0.0.0/8
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: fd00::/8
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: fe80::/10
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 192.0.2.0/24
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 198.51.100.0/24
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 203.0.113.0/24
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 255.255.255.255/32
/etc/unbound/unbound.conf/pi-hole.conf:    private-address: 2001:db8::/32





Mike




SpartanVXL
1498 posts

Uber Geek
+1 received by user: 666


  #3398567 30-Jul-2025 23:45
Send private message

I’m taking a guess but anything to do with permissions? I think I see systemd is exiting on the unbound helper at chroot_setup.


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.