Hi John, thanks for taking the time to file this bug report and help make Ubuntu better!
It would appear that this happens because the mysql server is stopped some time before configuration (maybe preinst?) and then not started again. I think this may be because bacula-director-mysql only *recommends* mysql-server, it does not (and should not) depend on mysql- server. I'm not sure how we can guarantee that mysql has been installed, configured fully, and started before bacula is configured. To recreate the problem: I spun up a Lucid VM and just ran: sudo apt-get install bacula-director-mysql And experienced the same sequence as your DpkgTerminalLog.txt shows. To work around the problem, after the process, ignore the error after dbconfig, then run: sudo dpkg-reconfigure bacula-director-mysql After everything finishes being configured. The alternative is to install mysql-server *first*, then install bacula-mysql-director. Marking as Triaged, as I think there is enough information to begin working on a fix. Setting importance to Medium, as this will most likely affect anybody who tries to install bacula-director-mysql without pre-configuring their mysql-server. ** Changed in: bacula (Ubuntu) Status: New => Triaged ** Changed in: bacula (Ubuntu) Importance: Undecided => Medium ** Summary changed: - package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + bacula-director-mysql fails configuration because mysql-server is not running -- bacula-director-mysql fails configuration because mysql-server is not running https://bugs.launchpad.net/bugs/633789 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs