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

[Julián Corcuera]

Binary package hint: bacula

Failed on Bakula install configuration on 10.10 (already installed, from beta media) from Synaptic. Synaptic simply stated that an error had occurred, and stopped there, waiting for me to stop the install. Install was with a bunch of other stuff, so perhaps something caused a conflict there.

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: bacula-director-mysql 5.0.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Oct 13 20:52:29 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
SourcePackage: bacula
Title: package bacula-director-mysql 5.0.2-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[James Page (james-page)]

Error from message log:

dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf

Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2).

unable to connect to mysql server.

error encountered creating user:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Bacula fails to configure as MySQL is not running during the configuration step; this can be worked around by upgrading/installing mysql-server before bacula.

[James Page (james-page)]

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 616754, 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.