Ubuntu
unbound package

unbound DNS service crashing/not starting

Bug #1913216 reported by Greg Zingler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unbound (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I try to install unbound on a clean install of Ubuntu Server 20.4.1, I get an error:

==========Screen Output==============
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
invoke-rc.d: initscript unbound, action "start" 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 Mon 2021-01-25 20:37:44 UTC; 7ms ago
       Docs: man:unbound(8)
    Process: 2369 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
    Process: 2372 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
    Process: 2376 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, status=1/FAILURE)
   Main PID: 2376 (code=exited, status=1/FAILURE)
Processing triggers for systemd (245.4-4ubuntu3.4) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
==========End Screen Output==============

The DNS service will not work and so Pi-Hole and its FTL service also fail.

This seems to be after the most recent Ubuntu updates, because I was having no problems until this week, and the Ubuntu Focal Unbound has not been updated since May 2020.

Revision history for this message
Haw Loeung (hloeung) wrote :

What does 'journalctl -xe' say? Also anything interesting in /var/log/syslog?

Revision history for this message
Greg Zingler (gregz83) wrote :

I'm probably going to close this bug report tomorrow. Giving this 24 hours but after reinstalling and re-configuring both Pi-Hole and Unbound, everything is working.
If it fails again I will provide updates including the output of jornalctl -xe, otherwise I will just close/cancel my bug report. Thank you.

Here is the link to the entire discussion I had in the Pi-Hole forum:
https://discourse.pi-hole.net/t/ftl-failed-to-start-since-last-update/43578/15

Revision history for this message
Greg Zingler (gregz83) wrote :

This is no longer an issue for me, although I am not sure what caused the failure in the first place the required 2 complete reinstalls.

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thanks for the bug report and for following up on it. I tried creating a Focal VM and installing unbound in it, and it succeeded. Since it is not clear how to reproduce the issue, and no logs were provided, I am marking this bug as Incomplete. If you happen to find more details about the problem and can provide a reliable way to reproduce it, feel free to mark the bug as New again. Thanks!

Changed in unbound (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unbound (Ubuntu) because there has been no activity for 60 days.]

Changed in unbound (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.