Package: unbound
Version: 1.22.0-2+deb13u3
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

Unbound fails to start when the system is booted. I have unbound
running on Debian 13 and on a Raspberry Pi also running Trixie,
and the same happens at every boot on both platforms. 

After the system comes up, I need to use systemctl to manually
restart unbound, then it comes up and works without problems.

In the log, journalctl only says this:


 The unit unbound.service has entered the 'failed' state with result 
'exit-code'.
░░ Automatic restarting of the unit unbound.service has been schedul>
░░ the configured Restart= setting for the unit.
Jun 24 22:00:12 ghost systemd[1]: unbound.service: Start request rep>
Jun 24 22:00:12 ghost systemd[1]: unbound.service: Failed with resul>
░░ Subject: Unit failed
░░ Defined-By: systemd


-- System Information:
Debian Release: 13.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.0.10+deb13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unbound depends on:
ii  adduser              3.152
ii  init-system-helpers  1.69~deb13u1
ii  libc6                2.41-12+deb13u3
ii  libevent-2.1-7t64    2.1.12-stable-10+b1
ii  libhiredis1.1.0      1.2.0-6+b3
ii  libnghttp2-14        1.64.0-1.1+deb13u1
ii  libprotobuf-c1       1.5.1-1
ii  libpython3.13        3.13.5-2+deb13u2
ii  libssl3t64           3.5.6-1~deb13u2
ii  libsystemd0          257.13-1~deb13u1

Versions of packages unbound recommends:
ii  dns-root-data  2025080400~deb13u1

Versions of packages unbound suggests:
ii  apparmor  4.1.0-1
ii  openssl   3.5.6-1~deb13u2

-- Configuration Files:
/etc/unbound/unbound.conf.d/remote-control.conf changed:
remote-control:
  control-enable: no
  # by default the control interface is is 127.0.0.1 and ::1 and port 8953
  # it is possible to use a unix socket too
  control-interface: /run/unbound.ctl


-- no debconf information

Reply via email to