[pkg-bacula-devel] Bug#825064: Bug#825064: Bacula director does not start silently due to database mismatch

Carsten Leonhardt leo at debian.org
Mon May 23 11:31:44 UTC 2016


Hi Klaus,

did you allow dbconfig common to update the database? Please send the
output of:

fgrep dbc_upgrade /etc/dbconfig-common/bacula-director-sqlite3.conf

If it shows dbc_upgrade='true', could you please check for relevant
messages in /var/log/apt/term.log around the line

"applying upgrade sql for 7.0.5+dfsg-4 -> 7.2.0"

Here, I've just re-tested upgrading on my test
machine, the database update works automatically and the director is
running after the update.

If you didn't allow the automatic upgrade, you can find the update
script in /usr/share/bacula-director/update_sqlite3_tables. Please copy
that and change "db_name=XXX_DBNAME_XXX" to "db_name=bacula" before
running it. That's due to an oversight I just noticed because of a last
minute change to work around something else.

Yours,

Carsten / leo



More information about the pkg-bacula-devel mailing list