package bacula-director-mysql (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10

[Dan Pitic]

Binary package hint: bacula

I tried removing bacula director and bacula mysql and I assumed the operation was successful. After logging back in sometime later, I got a message saying there was a problem with bacula-director-mysql.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bacula-director-mysql (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering:
 bacula-director-mysql: Remove
 bacula-common-mysql: Remove
 bacula-director-common: Remove
Architecture: amd64
Date: Sat Apr 30 14:03:41 2011
ErrorMessage: subprocess installed pre-removal script returned error exit status 10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: bacula
Title: package bacula-director-mysql (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10
UpgradeStatus: Upgraded to natty on 2011-04-30 (1 days ago)

[Andres Rodriguez (andreserl)]

Hi there,

thank you for taking the time to report bugs and trying to make Ubuntu better.

It seems that when trying to remove the package, bacula tries to connect to the mysql datbase to dump it, maybe as a backup. However, it is unable to do so as it seems that the credentials (user/password) are incorrect or when installed, the creation of the user wasn't complete and now it is trying to do it.

Could you please verify that bacula can connect to the MySQL server, or try to reinstall the package and remove it again?

Thank you again. Marking this bug as incomplete for now.

[Dan Pitic (dpitic)]

Yes, the problem did occur during removal and I was only able to enter the mysql password once. At the time, it was unclear whether dpkg was asking for the mysql bacula user password or the mysql admin password. I incorrectly assumed it was asking for the mysql bacula password, when instead it actually wanted the mysql admin password. There was no way I could see of going back and re-entering the password.

I removed all of the bacula packages and re-installed just the bacula client package. Everything is working fine now.

I guess the problem wasn't actually with bacula, but more so with dpkg not allowing me to re-enter the incorrect password and also not being specific enough about which mysql user it wanted a password for.

Thanks for your quick response time with this issue. Should I open up a new bug for dpkg and transfer this description there?

[Launchpad Janitor (janitor)]

[Expired for bacula (Ubuntu) because there has been no activity for 60 days.]