Karmic: Bind9 startup script fails after upgrade

[Adilson]

Binary package hint: bind9

Info:

$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

$ apt-cache policy bind9
bind9:
  Installed: 1:9.6.1.dfsg.P1-3ubuntu0.2
  Candidate: 1:9.6.1.dfsg.P1-3ubuntu0.2
  Version table:
 *** 1:9.6.1.dfsg.P1-3ubuntu0.2 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        500 http://security.ubuntu.com karmic-security/main Packages
        100 /var/lib/dpkg/status
     1:9.6.1.dfsg.P1-3 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

Problem:

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed
  libdns53
The following packages have been kept back:
  empathy
The following packages will be upgraded:
  bind9 bind9-host bind9utils devicekit-disks dnsutils libbind9-50 libdns50
  libisc50 libisccc50 libisccfg50 liblwres50
11 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 1,668kB of archives.
After this operation, 81.9kB of additional disk space will be used.
Do you want to continue [Y/n]? y
..........................
.........................
..........................

(Reading database ... 171125 files and directories currently installed.)
Preparing to replace dnsutils 1:9.6.1.dfsg.P1-3 (using .../dnsutils_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement dnsutils ...
Preparing to replace bind9-host 1:9.6.1.dfsg.P1-3 (using .../bind9-host_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement bind9-host ...
Preparing to replace bind9 1:9.6.1.dfsg.P1-3 (using .../bind9_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement bind9 ...
Preparing to replace libbind9-50 1:9.6.1.dfsg.P1-3 (using .../libbind9-50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement libbind9-50 ...
Preparing to replace libisccfg50 1:9.6.1.dfsg.P1-3 (using .../libisccfg50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement libisccfg50 ...
Preparing to replace libisccc50 1:9.6.1.dfsg.P1-3 (using .../libisccc50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement libisccc50 ...
Preparing to replace liblwres50 1:9.6.1.dfsg.P1-3 (using .../liblwres50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement liblwres50 ...
Preparing to replace bind9utils 1:9.6.1.dfsg.P1-3 (using .../bind9utils_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement bind9utils ...
Preparing to replace libisc50 1:9.6.1.dfsg.P1-3 (using .../libisc50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement libisc50 ...
Preparing to replace libdns50 1:9.6.1.dfsg.P1-3 (using .../libdns50_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Unpacking replacement libdns50 ...
Selecting previously deselected package libdns53.
Unpacking libdns53 (from .../libdns53_1%3a9.6.1.dfsg.P1-3ubuntu0.2_i386.deb) ...
Preparing to replace devicekit-disks 007-2ubuntu3 (using .../devicekit-disks_007-2ubuntu4_i386.deb) ...
Unpacking replacement devicekit-disks ...
Processing triggers for man-db ...
Processing triggers for ufw ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up libisc50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up libdns53 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up libisccc50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up libisccfg50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up libbind9-50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up liblwres50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up bind9-host (1:9.6.1.dfsg.P1-3ubuntu0.2) ...
Setting up dnsutils (1:9.6.1.dfsg.P1-3ubuntu0.2) ...

Setting up bind9utils (1:9.6.1.dfsg.P1-3ubuntu0.2) ...
Setting up bind9 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...
#
 * Starting domain name service... bind9 [fail]
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: error processing bind9 (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up libdns50 (1:9.6.1.dfsg.P1-3ubuntu0.2) ...
Setting up devicekit-disks (007-2ubuntu4) ...

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)

>>>>>>>>>>>>>>>>>>>>>>>>>>>

As can be seen above bind9 seems not to start again, I assume it is something with the startup script which has changed somehow, however, I wouldn't know how to go identifying the problem if some could please look into this and tell me how to sort it out I would be grateful.

ProblemType: Package
Architecture: i386
Date: Mon Dec 7 21:08:12 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: bind9 1:9.6.1.dfsg.P1-3ubuntu0.2
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: bind9
Title: package bind9 1:9.6.1.dfsg.P1-3ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-16-generic i686

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

Could you please attach the file /var/log/daemon.log to this report ?

[Adilson (adilson-moco)]

I have attached it, hope it helps

[Jean-Baptiste Lallement (jibel)]

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.