** Attachment removed: VarLogDistupgradeSystemstatetargz.gz
https://bugs.launchpad.net/bugs/588104/+attachment/1411354/+files/VarLogDistupgradeSystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
** Attachment removed: VarLogDistupgradeSystemstatetargz.gz
https://bugs.launchpad.net/bugs/588104/+attachment/1411354/+files/VarLogDistupgradeSystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for bacula (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bacula (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in ubuntu.
[Expired for bacula (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bacula (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588104
The same problem:
Setting up bacula-director-mysql (5.0.1-1ubuntu1) ...
debconf: Unknown template field '_description', in stanza #9 of
/var/lib/dpkg/info/bacula-director-mysql.templates
dbconfig-common: writing config to
The same problem:
Setting up bacula-director-mysql (5.0.1-1ubuntu1) ...
debconf: Unknown template field '_description', in stanza #9 of
/var/lib/dpkg/info/bacula-director-mysql.templates
dbconfig-common: writing config to
- MySQL was definietely run well before the upgrade
did you mean running ?
It sure would seem to me that the likely issue was that mysql server was
not running when you started the upgrade. Nothing in the logs attached
would seem to indicate that mysql was shut down.
** Changed in: bacula
Yes, I meant MySQL was running before the OS upgrade. Actually there is
a log entry in VarLogDistupgradeApttermlog.gz which shows that it had
been running for about a month. I had the feeling that MySQL was stopped
by the upgrade script before the bacula upgrade, and indeed I saw a few
lines
- MySQL was definietely run well before the upgrade
did you mean running ?
It sure would seem to me that the likely issue was that mysql server was
not running when you started the upgrade. Nothing in the logs attached
would seem to indicate that mysql was shut down.
** Changed in: bacula
Yes, I meant MySQL was running before the OS upgrade. Actually there is
a log entry in VarLogDistupgradeApttermlog.gz which shows that it had
been running for about a month. I had the feeling that MySQL was stopped
by the upgrade script before the bacula upgrade, and indeed I saw a few
lines
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49474430/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/49474431/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
At the end of the OS upgrade, Ubuntu displays A recovery will run now
(dpkg --configure -a). After this it again attempts to upgrade the
bacula database, and it seems it have completed successfully.
--
package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: ERROR
2002 (HY000):
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49474430/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/49474431/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
At the end of the OS upgrade, Ubuntu displays A recovery will run now
(dpkg --configure -a). After this it again attempts to upgrade the
bacula database, and it seems it have completed successfully.
--
package bacula-director-mysql 5.0.1-1ubuntu1 failed to install/upgrade: ERROR
2002 (HY000):
14 matches
Mail list logo
