package bacula-director-mysql 2.4.2-1ubuntu6 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bacula
On a Hardy server I had finally been able to get bacula 2.2.8 to install by having mysql up and running first before the bacula install. On this Intrepid laptop I was trying to install bacula 2.4.2 for testing. I had tried the bacula install on a virgin, new system install and it had failed with a similar message. This time after (I thought) cleaned out all the leftover bacula dregs I installed mysql-server first and then tried to install bacula. I first made sure that there was no leftover bacula database with:
mysqladmin -u root -p drop bacula
to which the system replied it knew nothing about bacula (so good so far).
When I tried to do an install with:
sudo apt-get install bacula
it did not bring up the terminal queries for things like db administrator passwords, database names or database passwords. It simply failed and hung the whole system with it. After a forced reboot the system came here. The bacula-fd and bacula-sd daemons are running but not the director. The /etc/bacula/
I would play with this some more if I could figure out how to REALLY get all of the bacula stuff off the machine. Reinstalling the system from scratch gets old.
- Does anyone know how to, absolutely/
- Anybody have any idea of how to install bacula on an Intrepid system? I've never been able to make it succeed.
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: bacula-
SourcePackage: bacula
Title: package bacula-
Uname: Linux 2.6.27-7-generic i686
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 293515, 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.