Ubuntu
bacula package

package bacula-director-mysql 5.0.3-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #836875 reported by Pavel Mlčoch on 2011-08-29

This bug report is a duplicate of: Bug #321091: Bacula fails to install correctly if mysql wasn't installed before. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bacula (Ubuntu)	New	Undecided	Unassigned

Bug Description

crash on install

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: bacula-director-mysql 5.0.3-1ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Aug 28 18:22:02 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110827)
SourcePackage: bacula
Title: package bacula-director-mysql 5.0.3-1ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Pavel Mlčoch (pavkamlc) wrote on 2011-08-29:

AptOrdering.txt Edit (645 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (646 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (60.4 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (101.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (22.1 KiB, application/x-gzip)
DuplicateSignature.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2011-08-29

tags:

removed: need-duplicate-check

Revision history for this message

James Page (james-page) wrote on 2011-09-01:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 563039, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.