Since Jaunty is EOL, closing Jaunty task as Won't Fix.
** Changed in: bacula (Ubuntu Jaunty)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
This should be fixed for karmic since its a problem with dbconfig-
common.
Regards
chuck
** Changed in: bacula (Ubuntu)
Status: Incomplete = Fix Released
--
intrepid - jaunty upgrade fails [for default bacula installs]
https://bugs.launchpad.net/bugs/363077
You received this bug
@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.
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
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.
--
intrepid - jaunty upgrade fails [for default bacula
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
