Package: bacula-director-pgsql
Version: 5.0.2-1~bpo50+1
Severity: normal
Hi!
This bug describes the identical problem as #584791 does, but since that bug
was closed due to lack of response from the original submitter and I don't
know how (if) reportbug can reopen a bug I submit this new one.
(and I guess mentioning backports in the subject is good, too)
I just tried to upgrade the bacula installation on a lenny machine from 2.4.4
to lenny-backports (currently the same version as in squeeze: 5.0.2).
During the automatic database upgrade I got the following message:
| An error seems to have occurred while upgrading the database. If it's of any
help, this was the error encountered:
|
| NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"pathhierarchy_pkey" for table "pathhierarchy" NOTICE: CREATE TABLE / PRIMARY
KEY will create implicit index "pathvisibility_pkey" for
| table "pathvisibility" ERROR: relation "file_jpfid_idx" already exists
|
| Fortunately, there should be a backup of the database made just before the
upgrade in
/var/cache/dbconfig-common/backups/bacula-director-pgsql_2.4.4-1.pgsql.
|
| At this point, you have the option to retry or abort the operation. If you
choose "retry", you will be prompted with all the configuration questions once
more and another attempt will be made at
| performing the operation. "retry (skip questions)" will immediately attempt
the operation again, skipping all questions. If you choose "abort", the
operation will fail and you will need to downgrade,
| reinstall, reconfigure this package, or otherwise manually intervene to
continue using it.
|
| Error upgrading database for bacula-director-pgsql. Retry?
|
|
abort
|
retry
|
retry (skip questions)
|
|
|
<Ok>
Above is the dialog output, with scrolling back the terminal I see the first
dialog where I was asked:
| Perform upgrade on database for bacula-director-pgsql with dbconfig-common?
(which I answered with "Yes")
Between the two dialogs is the the script output:
creating database backup in
/var/cache/dbconfig-common/backups/bacula-director-pgsql_2.4.4-1.pgsql.
applying upgrade sql for 2.4.4-1 -> 3.0.0.
applying upgrade sql for 2.4.4-1 -> 5.0.0.
error encountered processing
/usr/share/dbconfig-common/data/bacula-director-pgsql/upgrade/pgsql/5.0.0:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"pathhierarchy_pkey" for table "pathhierarchy" NOTICE: CREATE TABLE / PRIMARY
KEY will create implicit index "pathvisibility_pkey" for table "pathvisibility"
ERROR: relation "file_jpfid_idx" already exists
On this machine I can live with not running bacula backups for some time, so
it is available for further analysis.
BTW, the directory /var/cache/dbconfig-common/backups and the contained file
bacula-director-pgsql_2.4.4-1.pgsql are world readable. Against which package
should this be reported?
Regards,
Thomas
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (550, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bacula-director-pgsql depends on:
ii bacula-common 5.0.2-1~bpo50+1 network backup, recovery and verif
pn bacula-common-pgsql <none> (no description available)
pn bacula-director-common <none> (no description available)
ii dbconfig-common 1.8.39 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18lenny4 GNU C Library: Shared libraries
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libpq5 8.3.11-0lenny1 PostgreSQL C client library
ii libssl0.9.8 0.9.8g-15+lenny7 SSL shared libraries
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra
ii postgresql-client 8.3.11-0lenny1 front-end programs for PostgreSQL
ii postgresql-client-8.3 [ 8.3.11-0lenny1 front-end programs for PostgreSQL
ii python2.5 2.5.2-15+lenny1 An interactive high-level object-o
Versions of packages bacula-director-pgsql recommends:
ii postgresql-8.3 8.3.11-0lenny1 object-relational SQL database, ve
Versions of packages bacula-director-pgsql suggests:
pn postgresql-contrib <none> (no description available)
pn postgresql-doc <none> (no description available)
-- debconf information:
bacula-director-pgsql/pgsql/authmethod-admin: ident
bacula-director-pgsql/pgsql/no-empty-passwords:
bacula-director-pgsql/upgrade-backup: true
bacula-director-pgsql/install-error: abort
bacula-director-pgsql/purge: false
bacula-director-pgsql/pgsql/method: unix socket
bacula-director-pgsql/db/app-user: bacula
bacula-director-pgsql/dbconfig-reinstall: false
bacula-director-pgsql/db/dbname: bacula
bacula-director-pgsql/remote/host:
bacula-director-pgsql/pgsql/admin-user: postgres
bacula-director-pgsql/internal/skip-preseed: false
bacula-director-pgsql/database-type: pgsql
bacula-director-pgsql/remote/port:
bacula-director-pgsql/remote/newhost:
bacula-director-pgsql/remove-error: abort
bacula-director-pgsql/passwords-do-not-match:
bacula-director-pgsql/internal/reconfiguring: false
bacula-director-pgsql/pgsql/authmethod-user: ident
bacula-director-pgsql/pgsql/manualconf:
* bacula-director-pgsql/dbconfig-install: true
bacula-director-pgsql/dbconfig-upgrade: true
bacula-director-pgsql/missing-db-package-error: abort
bacula-director-pgsql/dbconfig-remove:
bacula-director-pgsql/upgrade-error: abort
bacula-director-pgsql/pgsql/changeconf: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
