package bacula-director 7.4.4+dfsg-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1690645 reported by john swails
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

upgraded to 17.04 and started to receive this message

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bacula-director 7.4.4+dfsg-5
Uname: Linux 4.10.1-041001-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Sun May 14 10:45:11 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-05-21 (358 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: bacula
Title: package bacula-director 7.4.4+dfsg-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to zesty on 2017-04-15 (29 days ago)

Revision history for this message
john swails (john-swails) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi John,
thank you for your report.

From the log:
May 14 10:30:01 hostname systemd[1]: Failed to start Bacula Director Daemon service.
May 14 10:30:01 hostname systemd[1]: bacula-director.service: Failed with result 'exit-code'.
[...]
May 14 10:45:11 hostname systemd[1]: Failed to start Bacula Director Daemon service.
May 14 10:45:11 hostname systemd[1]: bacula-director.service: Failed with result 'exit-code'.

The former could be from your boot (the log isn't long enough to see that for sure). According to DpkgHistoryLog it at least is not from a former try to upgrade.

So the TL;DR on most of this kind of issues is that if you have a service with a broken config (e.g. you experimented with it but it never worked) will fail to upgrade as it requires to restart the service.

If you don't use bacula anyway, apt purge it.
If you do so please get it configured so that it can start - afterwards an upgrade will succeed.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or 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.

Changed in bacula (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

You might also look into
$ systemctl status bacula-director.service
as reported by the failed upgrade - maybe it indicates the problem the service has to start.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bacula (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.