Package: unbound
Version: 1.22.0-2
Severity: important
Dear Maintainer,
* What led up to the situation?
I recently just upgraded my Proxmox host from Debian 12 to 13 as well as
Proxmox 8 to 9. Upon reboot, my existing/working installation of unbound did
not start
* What exactly did you do (or not do) that was effective (or
ineffective)?
After troubleshooting, I determined something in the stock AppArmor
profile was blocking unbound from starting. Putting the unbound AppArmor
profile into complain mode yielded ambiguous socket denial errors. Disabling
the AppArmor profile allowed unbound to start correctly. I also purged my
existing unbound install (reverting to stock configs) and it too would not start
* What was the outcome of this action?
unbound started correctly with the AppArmor profile disabled or put into
complain mode
* What outcome did you expect instead?
Stock unbound to start correctly
-- System Information:
Debian Release: 13.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.14.8-2-pve (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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.68
ii libc6 2.41-12
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
ii libprotobuf-c1 1.5.1-1
ii libpython3.13 3.13.5-2
ii libssl3t64 3.5.1-1
ii libsystemd0 257.7-1
Versions of packages unbound recommends:
ii dns-root-data 2024071801
Versions of packages unbound suggests:
ii AppArmor 4.1.1-pmx1
ii openssl 3.5.1-1
-- no debconf information
