Ubuntu
bacula package

bacula-director-mysql fails configuration because mysql-server is not running

Bug #633789 reported by John Robinson on 2010-09-09

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)	Triaged	Medium	Unassigned

Bug Description

Binary package hint: bacula

Was installing bacula using synaptic. Error of crash was reported during the install. This system is in a virtual machine just for testing of the new Ubuntu system, and as such is relatively virgin without much installed on it..... (Just wanted to see.....)

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-director-mysql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
Architecture: amd64
Date: Wed Sep 8 23:24:27 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: bacula
Title: package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

John Robinson (dayhawk) wrote on 2010-09-09:

AptOrdering.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (22.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (72.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Clint Byrum (clint-fewbar) wrote on 2010-09-10:

Hi John, thanks for taking the time to file this bug report and help make Ubuntu better!

It would appear that this happens because the mysql server is stopped some time before configuration (maybe preinst?) and then not started again. I think this may be because bacula-director-mysql only *recommends* mysql-server, it does not (and should not) depend on mysql-server.

I'm not sure how we can guarantee that mysql has been installed, configured fully, and started before bacula is configured.

To recreate the problem:

I spun up a Lucid VM and just ran:

sudo apt-get install bacula-director-mysql

And experienced the same sequence as your DpkgTerminalLog.txt shows.

To work around the problem, after the process, ignore the error after dbconfig, then run:

sudo dpkg-reconfigure bacula-director-mysql

After everything finishes being configured. The alternative is to install mysql-server *first*, then install bacula-mysql-director.

Marking as Triaged, as I think there is enough information to begin working on a fix.

Setting importance to Medium, as this will most likely affect anybody who tries to install bacula-director-mysql without pre-configuring their mysql-server.

Changed in bacula (Ubuntu):
status:	New → Triaged
importance:	Undecided → Medium
summary:	- package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: - subprocess installed post-installation script returned error exit status - 1 + bacula-director-mysql fails configuration because mysql-server is not + running