bacula-director-mysql fails to authenticate against mysql on upgrade

Bug #1019133 reported by Dan Pitic
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Invalid
High
Unassigned

Bug Description

MySQL database root users requires a password. There is no prompt to enter this password. Therefore the upgrade cannot be completed using the normal Bacula upgrade process.

Description: Ubuntu 12.04 LTS
Release: 12.04

Expected:
Prompt to enter the MySQL root password to allow the database update to be performed.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bacula-director-mysql 5.2.5-0ubuntu6.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 29 12:43:21 2012
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.2.5-0ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-05-14 (46 days ago)

Revision history for this message
Dan Pitic (dpitic) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

There is logic to make this happen - the package uses the dbconfig-common package to provide all the necessary logic. So I think that this is either a local misconfiguration, or there is a bug in bacula-director-mysql in the way that it uses dbconfig-common, or there is a bug in dbconfig-common.

Do you know if this bug is reproducible, and if so do you have exact steps to reproduce it?

Changed in bacula (Ubuntu):
importance: Undecided → High
summary: - package bacula-director-mysql 5.2.5-0ubuntu6.1 failed to
- install/upgrade: subprocess installed post-installation script returned
- error exit status 1
+ bacula-director-mysql fails to authenticate against mysql on upgrade
Revision history for this message
Dan Pitic (dpitic) wrote :

I can't reproduce this bug because the Bacula update succeeded. Just the DB upgrade failed. This causes the Bacula director to fail to start.

The problem started when I upgraded from Ubuntu 11.10 to 12.04. I haven't got the relevant Bacula bug reference for this, but I did get notifications that it had been corrected, hence the current Bacula version, which is successfully installed on my machine now.

I've seen other MySQL upgrades which ask for the root MySQL password. This did not happen during the Bacula DB upgrade.

Let me know if there is any other information I can provide.

I guess, if nobody else is affected by this bug, then I must have some local misconfiguration. Either way, it should not have happened. Bacula was fully functional in 11.10, and problems only started when I upgraded to 12.04.

Revision history for this message
Dan Pitic (dpitic) wrote :

A strange series of events just happened which lead to the successful conversion of the bacula DB. This is what happened:

Initially, I had been using Gnome shell. I logged out because I couldn't access my contacts in Evolution. I logged into Unity and I can access my Evolution contacts (which are GMail contacts).

I added an external ppa to install some extra icons.

Using Synaptic package manager, I selected the icon packages I wanted to and applied the changes. During the icon package install, a window opened up asking for the MySQL root password. There is not normally a connection between the icons and MySQL.

I can't explain how this happened and why the MySQL password window started up, but the end result is that the Bacula DB has been correctly upgraded and the director is now running correctly.

As far as I'm concerned, this is no longer a bug for me.

Thank you for all your help. If you can offer some explanation, I'm willing to read it.

Revision history for this message
Robie Basak (racb) wrote :

Dan,

It sounds like the package manager tried to fix all unconfigured packages (as it is designed to) and this time you got the prompt for the password.

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.