package bind9 1:9.9.5.dfsg-3ubuntu0.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
this error presented when I was doing an upgrade.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bind9 1:9.9.5.
ProcVersionSign
Uname: Linux 3.16.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Mon Sep 14 10:16:46 2015
DuplicateSignature: package:
ErrorMessage: subprocess installed post-installation script returned error exit status 100
InstallationDate: Installed on 2015-03-25 (172 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
KernLog:
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
bind9utils 1:9.9.5.
apparmor 2.8.95~
SourcePackage: bind9
SyslogBind9:
Sep 14 10:02:34 Spooner kernel: [ 680.471438] systemd-
Sep 14 10:23:43 Spooner kernel: [ 1950.760941] systemd-
Sep 14 11:17:00 Spooner kernel: [ 5151.076783] systemd-
Title: package bind9 1:9.9.5.
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
mtime.conffile.
tags: | removed: need-duplicate-check |
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu. Specifically you appear to have deleted bind9 configuration files on your system, so the bind9 service cannot be expected to work.
You can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.
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, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.