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

Bug #712291 reported by Keminda Ruberu on 2011-02-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: bacula

Pls send

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula-director-mysql 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic i686
Architecture: i386
Date: Thu Feb 3 10:09:05 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (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

Keminda Ruberu (kemindaruberu) wrote :
Scott Moser (smoser) wrote :

I've seen bugs like this before. mysql isn't running, but bacula-directory-mysql wsa trying to talk to it:

| Setting up bacula-director-mysql (5.0.1-1ubuntu1) ...
| debconf: Unknown template field '_description', in stanza #9 of /var/lib/dpkg/info/bacula-director-mysql.templates
| 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)
| dbconfig-common: bacula-director-mysql configure: aborted.
| dbconfig-common: flushing administrative password
| dpkg: error processing bacula-director-mysql (--configure):
| subprocess installed post-installation script returned error exit status 1

It seems to me that this is actually a bug in the configure script of bacula. It clearly is depending on something being installed, but, per [1]:
   Note: Note that the config script is run before the package is unpacked. It
   should only use commands that are in essential packages Also, it shouldn't
   actually edit files on the system, or affect it in any other way.

I'm not really sure how this can be fixed, though.
--
[1] http://www.fifi.org/doc/debconf-doc/tutorial.html

Changed in bacula (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers