The issue I am facing:
I'm setting up PiHole + Unbound on a new RP4 and running into a problem after following the "Required for Bullseye+" steps at the bottom of the unbound - Pi-hole documentation tutorial. All the steps proceed normally without error until the final step of restarting unbound, which returns an error:
> WaynePi2@pihole2:~ $ sudo service unbound restart
> Job for unbound.service failed because the control process exited with error code.
> See "systemctl status unbound.service" and "journalctl -xe" for details.
Output of both of those commands:
systemctl status unbound.service
WaynePi2@pihole2:~ $ systemctl status unbound.service
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2023-08-05 00:29:50 EDT; 7s ago
Docs: man:unbound(8)
Process: 1201 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
Process: 1204 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
Process: 1207 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
Process: 1208 ExecStopPost=/usr/lib/unbound/package-helper chroot_teardown (code=exited, status=0/SUCCESS)
Main PID: 1207 (code=exited, status=1/FAILURE)
CPU: 68ms
Aug 05 00:29:50 pihole2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Aug 05 00:29:50 pihole2 systemd[1]: Stopped Unbound DNS server.
Aug 05 00:29:50 pihole2 systemd[1]: unbound.service: Start request repeated too quickly.
Aug 05 00:29:50 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
Aug 05 00:29:50 pihole2 systemd[1]: Failed to start Unbound DNS server.
Journalctl -xe
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1827 and the job result is failed.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 05 00:14:44 pihole2 systemd[1]: Stopped Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 1893 and the job result is done.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Start request repeated too quickly.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1893 and the job result is failed.
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 05 00:17:01 pihole2 CRON[1075]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session closed for user root
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Timed out waiting for reply from 152.67.232.7:123 (2.debian.pool.ntp.org).
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Initial synchronization to time server 162.159.200.123:123 (2.debian.pool.ntp.org).
Aug 05 00:22:37 pihole2 systemd[1]: Starting Cleanup of Temporary Directories...
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has begun execution.
░░
░░ The job identifier is 1959.
Aug 05 00:22:37 pihole2 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
Aug 05 00:22:37 pihole2 systemd[1]: Finished Cleanup of Temporary Directories.
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has finished successfully.
░░
░░ The job identifier is 1959.
...skipping...
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ An ExecStart= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1827 and the job result is failed.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 05 00:14:44 pihole2 systemd[1]: Stopped Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 1893 and the job result is done.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Start request repeated too quickly.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1893 and the job result is failed.
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 05 00:17:01 pihole2 CRON[1075]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session closed for user root
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Timed out waiting for reply from 152.67.232.7:123 (2.debian.pool.ntp.org).
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Initial synchronization to time server 162.159.200.123:123 (2.debian.pool.ntp.org).
Aug 05 00:22:37 pihole2 systemd[1]: Starting Cleanup of Temporary Directories...
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has begun execution.
░░
░░ The job identifier is 1959.
Aug 05 00:22:37 pihole2 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
Aug 05 00:22:37 pihole2 systemd[1]: Finished Cleanup of Temporary Directories.
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has finished successfully.
░░
░░ The job identifier is 1959.
...skipping...
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ An ExecStart= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1827 and the job result is failed.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 05 00:14:44 pihole2 systemd[1]: Stopped Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 1893 and the job result is done.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Start request repeated too quickly.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1893 and the job result is failed.
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 05 00:17:01 pihole2 CRON[1075]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session closed for user root
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Timed out waiting for reply from 152.67.232.7:123 (2.debian.pool.ntp.org).
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Initial synchronization to time server 162.159.200.123:123 (2.debian.pool.ntp.org).
Aug 05 00:22:37 pihole2 systemd[1]: Starting Cleanup of Temporary Directories...
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has begun execution.
░░
░░ The job identifier is 1959.
Aug 05 00:22:37 pihole2 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
Aug 05 00:22:37 pihole2 systemd[1]: Finished Cleanup of Temporary Directories.
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has finished successfully.
░░
░░ The job identifier is 1959.
...skipping...
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ An ExecStart= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1827 and the job result is failed.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 05 00:14:44 pihole2 systemd[1]: Stopped Unbound DNS server.
░░ Subject: A stop job for unit unbound.service has finished
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A stop job for unit unbound.service has finished.
░░
░░ The job identifier is 1893 and the job result is done.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Start request repeated too quickly.
Aug 05 00:14:44 pihole2 systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 05 00:14:44 pihole2 systemd[1]: Failed to start Unbound DNS server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 1893 and the job result is failed.
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Aug 05 00:17:01 pihole2 CRON[1075]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 05 00:17:01 pihole2 CRON[1074]: pam_unix(cron:session): session closed for user root
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Timed out waiting for reply from 152.67.232.7:123 (2.debian.pool.ntp.org).
Aug 05 00:17:11 pihole2 systemd-timesyncd[311]: Initial synchronization to time server 162.159.200.123:123 (2.debian.pool.ntp.org).
Aug 05 00:22:37 pihole2 systemd[1]: Starting Cleanup of Temporary Directories...
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has begun execution.
░░
░░ The job identifier is 1959.
Aug 05 00:22:37 pihole2 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
Aug 05 00:22:37 pihole2 systemd[1]: Finished Cleanup of Temporary Directories.
░░ Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
░░ Defined-By: systemd
░░ Support: www.debian.org/support
░░
░░ A start job for unit systemd-tmpfiles-clean.service has finished successfully.
░░
░░ The job identifier is 1959.
WaynePi2@pihole2:~ $
Here's the weirdest part: from all of my research (including this very similar thread from a year ago: Failed to start unbound) the "solution" to my problem is the very same set of Bullseye-required steps that broke my unbound!
Can anyone make heads or tails out of this?? Thanks!
Details about my system:
Brand new RP4 running Raspberry Pi OS Lite 64bit (Debian Bullseye 2023-05-03)
Fully updated at the start of this process
No other software installed beyond PiHole and Unbound (this is my initial configuration)
