package bind9 1:9.8.1.dfsg.P1-4ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Miro Stanik]

package bind9 1:9.8.1.dfsg.P1-4ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.dfsg.P1-4ubuntu0.2
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Fri Jul 27 08:54:09 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
RelatedPackageVersions:
 bind9utils 1:9.8.1.dfsg.P1-4ubuntu0.2
 apparmor 2.7.102-0ubuntu3.1
SourcePackage: bind9
Title: package bind9 1:9.8.1.dfsg.P1-4ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.named: [modified]
modified.conffile..etc.bind.named.conf: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.named: 2012-07-23T13:20:47.148723
mtime.conffile..etc.bind.named.conf: 2012-07-23T13:14:21.416707

[Robie Basak (racb)]

Jul 27 08:54:11 MS-5901 named[7769]: loading configuration from '/etc/bind/named.conf'
Jul 27 08:54:11 MS-5901 named[7769]: /etc/bind/named.conf:12: open: /var/lib/samba/private/named.conf: file not found
Jul 27 08:54:11 MS-5901 named[7769]: loading configuration: file not found
Jul 27 08:54:11 MS-5901 named[7769]: exiting (due to fatal error)

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid.

Specifically, you have a customised bind9 configuration which looks for /var/lib/samba/private/named.conf which does not exist. This is causing your upgrade to fail.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, and then change the bug status back to New.