package bind9 1:9.11.4+dfsg-3ubuntu5.4 failed to install/upgrade: installed bind9 package post-installation script subprocess returned error exit status 1

[Gordon]

Was doing a routine update and bind9 failed to installed, couldn't write the /var/cache/bind directory. This machine was Trusty, then Xenial, Bionic and now Cosmic. So could be related to a do-release-upgrade process as I've used bind for development and testing for a long time now.

Here's my history, where it bombed and I ran update-grub, then change ownership and set file permissions, then tried to re-install the broken update, which seems to have worked, but the logs were still kept and submitted, thanks Launchpad :)

26194 2019-06-22 05:06:17 sudo apt-get update
26195 2019-06-22 05:07:05 sudo apt-get dist-upgrade

*** Here is breaks...

Cannot write... /var/cache/bind

and worse the initram-fs process failed, so I saved myself...

26196 2019-06-22 05:08:45 sudo update-grub
26197 2019-06-22 05:09:55 sudo chown root.bind /var/cache/bind
26198 2019-06-22 05:10:05 sudo chmod 775 /var/cache/bind
26199 2019-06-22 05:10:15 sudo service bind restart
26200 2019-06-22 05:10:21 sudo apt-get dist-upgrade
26201 2019-06-22 05:10:45 sudo service bind9 restart
26202 2019-06-22 05:10:48 sudo service bind9 status
26203 2019-06-22 05:10:58 sudo service bind9 stop
26204 2019-06-22 05:11:22 sudo update-grub
26205 2019-06-22 05:11:27 sudo updatedb
26206 2019-06-22 05:19:45 sudo reboot

* Here's where system rebooted and I'll filed this report. Keep us posted, thanks.

Found my solution from a previous Launchpad bug, might be related:
> https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: bind9 1:9.11.4+dfsg-3ubuntu5.4
ProcVersionSignature: Ubuntu 4.18.0-22.23-lowlatency 4.18.20
Uname: Linux 4.18.0-22-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Sat Jun 22 05:07:56 2019
ErrorMessage: installed bind9 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-01-19 (1249 days ago)
InstallationMedia: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.3)
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt 1.7.5
SourcePackage: bind9
Title: package bind9 1:9.11.4+dfsg-3ubuntu5.4 failed to install/upgrade: installed bind9 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apport: [deleted]

[Andreas Hasenack (ahasenack)]

Thanks for filing this bug in Ubuntu.

Indeed the complaint was that bind couldn't write to /var/cache/bind. Do you happen to know what it was set to? That would help in debugging how it reached that state.

The attached logs unfortunately do not have more information about that, only the failure after the permission was incorrect already. I'll mark this bug as incomplete for that reason, as we have no way to reproduce the issue.

If you are able to get more information about this, or show a way to reproduce the problem, then please comment here and switch the bug status back to "new".

[Gordon (linux-web-expert)]

Thanks for getting back to me, but unfortunately no I don't know the prior
permissions, but I will say my syslog is much cleaner now, so I think this
was residual from upgrade if that helps

Cheers,
Gordon

On Mon, Jun 24, 2019, 7:21 AM Andreas Hasenack <email address hidden>
wrote:

> Thanks for filing this bug in Ubuntu.
>
> Indeed the complaint was that bind couldn't write to /var/cache/bind. Do
> you happen to know what it was set to? That would help in debugging how
> it reached that state.
>
> The attached logs unfortunately do not have more information about that,
> only the failure after the permission was incorrect already. I'll mark
> this bug as incomplete for that reason, as we have no way to reproduce
> the issue.
>
> If you are able to get more information about this, or show a way to
> reproduce the problem, then please comment here and switch the bug
> status back to "new".
>
> ** Changed in: bind9 (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1833812
>
> Title:
> package bind9 1:9.11.4+dfsg-3ubuntu5.4 failed to install/upgrade:
> installed bind9 package post-installation script subprocess returned
> error exit status 1
>
> Status in bind9 package in Ubuntu:
> Incomplete
>
> Bug description:
> Was doing a routine update and bind9 failed to installed, couldn't
> write the /var/cache/bind directory. This machine was Trusty, then
> Xenial, Bionic and now Cosmic. So could be related to a do-release-
> upgrade process as I've used bind for development and testing for a
> long time now.
>
> Here's my history, where it bombed and I ran update-grub, then change
> ownership and set file permissions, then tried to re-install the
> broken update, which seems to have worked, but the logs were still
> kept and submitted, thanks Launchpad :)
>
> 26194 2019-06-22 05:06:17 sudo apt-get update
> 26195 2019-06-22 05:07:05 sudo apt-get dist-upgrade
>
> *** Here is breaks...
>
> Cannot write... /var/cache/bind
>
> and worse the initram-fs process failed, so I saved myself...
>
> 26196 2019-06-22 05:08:45 sudo update-grub
> 26197 2019-06-22 05:09:55 sudo chown root.bind /var/cache/bind
> 26198 2019-06-22 05:10:05 sudo chmod 775 /var/cache/bind
> 26199 2019-06-22 05:10:15 sudo service bind restart
> 26200 2019-06-22 05:10:21 sudo apt-get dist-upgrade
> 26201 2019-06-22 05:10:45 sudo service bind9 restart
> 26202 2019-06-22 05:10:48 sudo service bind9 status
> 26203 2019-06-22 05:10:58 sudo service bind9 stop
> 26204 2019-06-22 05:11:22 sudo update-grub
> 26205 2019-06-22 05:11:27 sudo updatedb
> 26206 2019-06-22 05:19:45 sudo reboot
>
> * Here's where system rebooted and I'll filed this report. Keep us
> posted, thanks.
>
> Found my solution from a previous Launchpad bug, might be related:
> > https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.10
> Package: bind9 1:9.11.4+dfsg-3ubuntu5.4
> ProcVersionSignature: Ubuntu 4.18.0-22.23-lowlatency 4.18.20
> Uname: Linux 4.18.0-22-lo...

[Andreas Hasenack (ahasenack)]

Let's leave the bug at "incomplete", and if new information arises, it can be added here.

[Launchpad Janitor (janitor)]

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