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

[WeberEInc]

Binary package hint: bind9

Version: Ubuntu 9.10 - the Karmic Koala

The latest update attempted to update Bind9 and says it fails in dpkg reporting the following:

E: bind9: subprocess installed post-installation script returned error exit status 1

(Reading database ... 222034 files and directories currently installed.)
Processing triggers for man-db ...
Setting up bind9 (1:9.6.1.dfsg.P1-3ubuntu0.4) ...
 * Stopping domain name service... bind9
resolvconf: Error: /etc/resolv.conf must be a symlink
invoke-rc.d: initscript bind9, action "restart" failed.
dpkg: error processing bind9 (--configure):
 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:
 bind9
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up bind9 (1:9.6.1.dfsg.P1-3ubuntu0.4) ...
 * Stopping domain name service... bind9
resolvconf: Error: /etc/resolv.conf must be a symlink
invoke-rc.d: initscript bind9, action "restart" failed.
dpkg: error processing bind9 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bind9

ProblemType: Package
Architecture: amd64
Date: Sat Dec 11 18:10:55 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: bind9 1:9.6.1.dfsg.P1-3ubuntu0.4
ProcVersionSignature: Ubuntu 2.6.31-22.69-server
SourcePackage: bind9
Title: package bind9 1:9.6.1.dfsg.P1-3ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-22-server x86_64

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug and helping to make ubuntu better.

The logs show that bind9 failed to start because /etc/resolv.conf was not a
symbolic link. Depending on where the file came from, could you try renaming
your existing one

   mv /etc/resolv.conf /etc/resolv.conf.orig

and then re-try restarting bind9?

[WeberEInc (edweber)]

Serge,

Thank you for your reply. While I did find that error message, I didn't
know why I would need to change the file and why it wasn't
programmatic-ally handled during the upgrade. I did a 'cat' of the
file which showed how it was created:

root@WebEntU2:/home/evweber# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 10.110.0.15

If the NetworkManager applet creates this file as a file instead of as a
symbolic link like Bind9 needs it would seem that one of them is in
error.

Please advise.

- Ed

On Thu, 2010-12-16 at 16:23 +0000, Serge Hallyn wrote:

> Thanks for reporting this bug and helping to make ubuntu better.
>
> The logs show that bind9 failed to start because /etc/resolv.conf was not a
> symbolic link. Depending on where the file came from, could you try renaming
> your existing one
>
> mv /etc/resolv.conf /etc/resolv.conf.orig
>
> and then re-try restarting bind9?
>
> ** Changed in: bind9 (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: bind9 (Ubuntu)
> Status: Invalid => Incomplete
>

[WeberEInc (edweber)]

This is an ongoing problem with every update. It appears that bind9 is still set to try to update and it keeps failing. With each crash I have had an opportunity to create a new bug report. For all of them that have occurred up to today, I have been skipping re-submitting a new bug report for the same bug. Today, I created a new bug and named it as a duplicate/continuation of this bug.

Please advise.

[Launchpad Janitor (janitor)]

[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.]