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

Bug #625008 reported by Eric Ross
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bacula

Wouldn't accept the administrators password.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-director-mysql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Thu Aug 26 19:19:23 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 10
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
SourcePackage: bacula
Title: package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

Revision history for this message
Eric Ross (eric-ross) wrote :
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Hi Eric, thanks for taking the time to file this bug report and working with us to make Ubuntu better.

This would appear to be because mysqld was stopped or configured in an incompatible way, as indicated by this message from DpkgTerminalLog.txt:

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

error #2 means "No such file or directory", which would only occur if mysqld was stopped, or the configuration was changed to move the socket file somewhere else.

mysqld must be started and configured to use /var/run/mysqld/mysqld.sock in order for the config values to be checked.

Try ensuring that mysqld is started and that the socket file exists, and then run

sudo dpkg-reconfigure bacula-director-mysql

Marking Invalid, if you encounter another error while configuring the package, I would encourage you to open a new bug report.

Changed in bacula (Ubuntu):
status: New → Invalid
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.