Hi,
I've reopened the bug, and as suggested by Paul cloned it to have a copy
filed against dbconfig-common.
Please use bug #825735 for the issue related to dbconfig-common, and bug
#825064 for the issue "bacula silently fails to start" due to database
errors, for which I am testing a fix.
clone 825064 -1
reassign -1 dbconfig-common
thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Fr den 27. Mai 2016 um 13:08 schrieb Paul Gevers:
> I'd like to note that while I was investigating what to write below, I
> discovered three unrelated issues in two packages in how they react with
> dpkg-reconfigure (in dbconfig-common and
Hi
tl;dr: In the (long) past, the question during migration was different
and extremely confusing with respect to the underlaying logic. Klaus
probably got the old question, opted out of assistance and now had
problems during the upgrade. With respect to the current situation in
all involved
Hi
Just a short note, I am in the process of writing a response to the
previous message, but it isn't finished yet and I need to check some
statements. Unfortunately, it is bedtime now.
Paul
PS: no need to to/cc me, I am subscribed to the bug
signature.asc
Description: OpenPGP digital
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Di den 24. Mai 2016 um 18:02 schrieb Paul Gevers:
> > Klaus is of the opinion that setting it to 'true' will reinstall the
> > database on updates, for that he quotes the question about
> > reinstallation asked when doing "dpkg-reconfigure ".
>
Hi all,
On 24-05-16 11:53, Carsten Leonhardt wrote:
> it would be very helpful if you - as the dbconfig-common maintainer -
> would be able to spare a few minutes to clear up the following issue,
> because the discussion is about dbconfig-common by now.
Sure.
> Klaus, the bug reporter, updated
Dear Paul,
it would be very helpful if you - as the dbconfig-common maintainer -
would be able to spare a few minutes to clear up the following issue,
because the discussion is about dbconfig-common by now.
Klaus, the bug reporter, updated from bacula 7.0.5 to 7.4.0. This
requires a database
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 23. Mai 2016 um 21:19 schrieb Carsten Leonhardt:
> >> I've tested an update from 7.0.5, with dbc_install='false' in
> >> /etc/dbconfig-common/bacula-director-sqlite3.conf. This time the update
> >> wasn't applied, apparently
Hi Klaus,
>> I've tested an update from 7.0.5, with dbc_install='false' in
>> /etc/dbconfig-common/bacula-director-sqlite3.conf. This time the update
>> wasn't applied, apparently dbconfig-common doesn't apply any changes
>> when this is set.
>>
>> Please change it back to 'true' and run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Carsten,
Am Mo den 23. Mai 2016 um 18:50 schrieb Carsten Leonhardt:
> > But as I told, that is nothing for a casual user nor should that be
> > needed without notice.
>
> Yes. That's why I'd like to understand why it didn't work automatically
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 23. Mai 2016 um 12:31 schrieb Carsten Leonhardt:
> did you allow dbconfig common to update the database? Please send the
Sure.
> output of:
>
> fgrep dbc_upgrade /etc/dbconfig-common/bacula-director-sqlite3.conf
~> fgrep
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: bacula-director-sqlite3
Version: 7.4.0+dfsg-1
Severity: grave
The latest upgrade from 7.0.5 to 7.4.0 broke director as it silently
refuses to start. Only starting it manually with -f reveals the problem
that the database was not converted
14 matches
Mail list logo
