The error is
=====
Dec 7 21:27:46 * named[8820]: loading configuration from '/etc/bind/named.conf'
Dec 7 21:27:46 * named[8820]: none:0: open: /etc/bind/named.conf: permission
denied
Dec 7 21:27:46 * named[8820]: loading configuration: permission denied
Dec 7 21:27:46 * named[8820]: exiting (due to fatal error)
=====
>From dmesg.log
[ 7994.914405] type=1503 audit(1260220092.305:24): operation="open" pid=8266
parent=8264 profile="/usr/sbin/named" requested_mask="r::" denied_mask="r::"
fsuid=116 ouid=116 name="/var/lib/named/etc/bind/named.conf"
It looks like you're running bind in a chroot but you haven't changed apparmor
profile to suite this setup.
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.
Don't hesitate to submit any new bug.
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Invalid
--
Karmic: Bind9 startup script fails after upgrade
https://bugs.launchpad.net/bugs/493781
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
