intrepid -> jaunty upgrade fails [for default bacula installs]

[Michael Vogt]

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.

[Ante Karamatić (ivoks)]

In bacula's log, there's info about postgresql not being started and bacula-director not being configured. This is not the reason why bacula-sd failed.

bacula-sd doesn't interact with sql database at all. I'll investigate what happened.

[Ante Karamatić (ivoks)]

I can't reproduce it. I've installed intrepid and then bacula-sd-pgsql bacula-sd bacula-director-pgsql. After that I did upgrade with DEBIAN_FRONTEND=noninteractive and everything worked well. I even tried without DEBIAN_FRONTEND=noninteractive.

Can you start it by runing /etc/init.d/bacula-sd start? It listens on port 9103. Could it be that something else is listening on that port?

[Michael Vogt (mvo)]

@Ante: Thanks, there is nothing listening on 9103 other than bacula-sd (I just checked on the ugpraded system). The upgraded system works fine. I think this is a problem that only manifests itself during upgrade when bacula-sd gets restarted but something is not quite like it is expecting it (e.g. some other service is needs not running).

What more info can I post? Is there some debug swtich I can use to get more log information?

[Ante Karamatić (ivoks)]

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?

[Chuck Short (zulcss)]

This should be fixed for karmic since its a problem with dbconfig-common.

Regards
chuck

[Clint Byrum (clint-fewbar)]

Since Jaunty is EOL, closing Jaunty task as Won't Fix.