bin9 and apparmor problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bind9
bind 1:9.6.0.dfsg.P1-2
See also http://
The apparmor profile does not allow bind9 to use a /var/lib/named change root
May 23 13:04:35 obiwan named[14416]: starting BIND 9.6.0-P1 -u bind -t /var/lib/named
May 23 13:04:35 obiwan named[14416]: built with '--prefix=/usr' '--mandir=
May 23 13:04:35 obiwan named[14416]: found 2 CPUs, using 2 worker threads
May 23 13:04:35 obiwan named[14416]: using up to 4096 sockets
May 23 13:04:35 obiwan named[14416]: loading configuration from '/etc/bind/
May 23 13:04:35 obiwan named[14416]: none:0: open: /etc/bind/
May 23 13:04:35 obiwan named[14416]: loading configuration: permission denied
May 23 13:04:35 obiwan named[14416]: exiting (due to fatal error)
ProblemType: Bug
Architecture: amd64
Date: Sat May 23 13:15:49 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: bind9 (not installed)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: bind9
Uname: Linux 2.6.30-5-generic x86_64
Well, Ubuntu ships bind9 with an apparmor profile, not a chroot. If you change its configuration to run in a chroot, you must obviously also change the apparmor configuration so that it matches your specific way of doing things.
Closing as Invalid, as this is not a bug.