Could not open 'local/usr.sbin.named'

Bug #1754981 reported by MartinL
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Debian)
Fix Released
Unknown
bind9 (Ubuntu)
Fix Released
High
Andreas Hasenack

Bug Description

Reloading service

sudo service apparmor reload

fails with

Mar 11 15:35:28 server apparmor[21163]: AppArmor parser error for /etc/apparmor.d/usr.sbin.named in /etc/apparmor.d/usr.sbin.named at line 69: Could not open 'local/usr.sbin.named'

In configuration there is included non-existing file local/usr.sbin.named, see

 # Site-specific additions and overrides. See local/README for details.
 #include <local/usr.sbin.named>

This file is part of bind 9.10 [1] but bind 9.11 not [2].

[1] https://packages.ubuntu.com/search?suite=artful&arch=any&searchon=contents&keywords=%2Fetc%2Fapparmor.d%2Flocal%2Fusr.sbin.named
[2] https://packages.ubuntu.com/search?suite=bionic&section=all&arch=any&keywords=%2Fetc%2Fapparmor.d%2Flocal%2Fusr.sbin.named&searchon=contents

Related branches

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Confirmed:
Mar 15 12:48:12 bionic-bind9 apparmor[1859]: AppArmor parser error for /etc/apparmor.d/usr.sbin.named in /etc/apparmor.d/usr.sbin.named at line 69: Could not open 'local/usr.sbin.named'
Mar 15 12:48:12 bionic-bind9 apparmor[1859]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 15 12:48:12 bionic-bind9 apparmor[1859]: AppArmor parser error for /etc/apparmor.d/usr.sbin.named in /etc/apparmor.d/usr.sbin.named at line 69: Could not open 'local/usr.sbin.named'
Mar 15 12:48:12 bionic-bind9 apparmor[1859]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 15 12:48:12 bionic-bind9 apparmor[1859]: ...fail!
Mar 15 12:48:12 bionic-bind9 systemd[1]: apparmor.service: Control process exited, code=exited status=123
Mar 15 12:48:12 bionic-bind9 systemd[1]: Reload failed for AppArmor initialization.

Changed in bind9 (Ubuntu):
status: New → Triaged
importance: Undecided → High
tags: added: server-next
Changed in bind9 (Ubuntu):
assignee: nobody → Andreas Hasenack (ahasenack)
Changed in bind9 (Ubuntu):
status: Triaged → In Progress
Changed in bind9 (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bind9 - 1:9.11.2.P1-1ubuntu4

---------------
bind9 (1:9.11.2.P1-1ubuntu4) bionic; urgency=medium

  * Fix apparmor profile filename (LP: #1754981)

 -- Andreas Hasenack <email address hidden> Thu, 15 Mar 2018 10:06:57 -0300

Changed in bind9 (Ubuntu):
status: In Progress → Fix Released
Changed in bind9 (Debian):
status: New → Fix Committed
Changed in bind9 (Debian):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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