As predicted, the winbindd part works but unbound still fails to start
with the same errors.
The worst problems are those where you are asking yourself how they
ever worked. I am definitely not the AppArmor resource you're looking
for; I completely defer to you on how to proceed.
On Fri, Aug 15,
427] audit: type=1400
audit(1755188295.870:900):apparmor="ALLOWED" operation="create"
class="net" info="failed protocol match" error=-13 profile="unbound"
pid=931028 comm="unbound" family="unix" sock_type="stream" protoc
it: type=1400 audit(1755186269.708:719):
apparmor="ALLOWED" operation="create" class="net" info="failed
protocol match" error=-13 profile="unbound" pid=913729 comm="unbound"
family="unix" sock_type="dgram" protocol=0 req
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 y
4 matches
Mail list logo
