← Back to team overview

ubuntu-bacula team mailing list archive

[Bug 363077] Re: intrepid -> jaunty upgrade fails [for default bacula installs]

 

Hm... I can't see bacula-sd being stopped before upgrade - it seams like
bacula-sd.prerm wasn't executed before upgrade or /etc/init.d/bacula-sd
wasn't executable during upgrade. Starting bacula-sd will fail if
another bacula-sd is already running.

Any debugging done now would be useless, since bacula-sd is running. It
failed only during upgrade. I tried reinstalling bacula-sd, but with no
effect (i was unable to reproduce the bug). Could you try that? apt-get
--reinstall install bacula-sd and see if bacula-sd is being stopped
before upgrade?

-- 
intrepid -> jaunty upgrade fails [for default bacula installs]
https://bugs.launchpad.net/bugs/363077
You received this bug notification because you are a member of Ubuntu
Bacula, which is subscribed to bacula in ubuntu.

Status in “bacula” source package in Ubuntu: Incomplete
Status in bacula in Ubuntu Jaunty: Incomplete

Bug description:
Binary package hint: bacula

When doing a automatic intrepid -> jaunty upgrade (with DEBIAN_FRONTEND=noninteractive) the package
"bacula-sd" fails to upgrade:
...
Setting up postgresql-client (8.3.7-1) ...^M
Setting up bacula-director-pgsql (2.4.4-1ubuntu5) ...^M
Installing new version of config file /etc/bacula/scripts/delete_catalog_backup ...^M
dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-pgsql.conf^M
*** WARNING: ucf was run from a maintainer script that uses debconf, but^M
             the script did not pass --debconf-ok to ucf. The maintainer^M
             script should be fixed to not stop debconf before calling ucf,^M
             and pass it this parameter. For now, ucf will revert to using^M
             old-style, non-debconf prompting. Ugh!^M
^M
             Please inform the package maintainer about this problem.^M
^M
Creating config file /etc/dbconfig-common/bacula-director-pgsql.conf with new version^M
dbconfig-common: flushing administrative password^M
Processing configuration ...Ok.^M
 * Stopping Bacula Director...^M
   ...done.^M
 * Starting Bacula Director...^M
   ...done.^M
^M
Setting up bacula-sd (2.4.4-1ubuntu5) ...^M
Installing new version of config file /etc/init.d/bacula-sd ...^M
 * Starting Bacula Storage daemon...^M
   ...fail!^M
invoke-rc.d: initscript bacula-sd, action "start" failed.^M
dpkg: error processing bacula-sd (--configure):^M
 subprocess post-installation script returned error exit status 1^M
...

The log indicates that can not connect to the postgresql database. I will attach the full terminal log of the upgrade.



References