Package: bacula-director-pgsql
Version: 1.38.9-10
Severity: normal
The failure may arise from my having responded improperly to the
installation questions. If so, this may be a documentation issue more
than anything. Even after the install I don't see much about how to
go from 1.36->1.38.
>From my install:
------------------------------------------------------------
Setting up bacula-director-pgsql (1.38.9-10) ...
Configuring bacula-director-pgsql
---------------------------------
bacula-director-pgsql must have a database installed and configured before it
can be used. If you like, this can be handled with
dbconfig-common.
If you are an advanced database administrator and know that you want to perform
this configuration manually, or if your database has already
been installed and configured, you should refuse this option. Details on what
needs to be done should most likely be provided in
/usr/share/doc/bacula-director-pgsql.
Otherwise, you should probably choose this option.
Configure database for bacula-director-pgsql with dbconfig-common? no
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-pgsql.conf
Creating config file /etc/dbconfig-common/bacula-director-pgsql.conf with new
version
Processing configuration .../usr/share/bacula-director/postinst-common: line
18: /etc/bacula/bacula-dir.conf.dpkg-tmp: No such file or directory
Ok.
Stopping Bacula Director: bacula-dir.
Starting Bacula Director: 07-Jun 18:57 bacula-dir: Fatal error: Version error
for database "bacula". Wanted 9, got 8
07-Jun 18:57 bacula-dir: Fatal error: Could not open database "bacula".
07-Jun 18:57 bacula-dir: Fatal error: Version error for database "bacula".
Wanted 9, got 8
07-Jun 18:57 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
failed.
----------------------------------------------------------
The key phrase, as I read it, was "if your database has already been
installed and configured, you should refuse this option." This caused
me to say "no", though even at the time I wasn't sure if "installed
and configured" meant a
1.38 database only. Obviously my responses didn't work.
It was and is not clear to me if the package or dbconfig-common
(1.8.13) provide any kind of upgrade facility. It wasn't clear to me
if upgrading was required; not it is clear that the answer is yes.
I'm uncertain how to proceed. The upstream documentation provided
with the package offers few clues, and even if it did it would be good
to say what the story is for Debian (particularly given the use of
dbconfig-common).
The only thing I've found after installation is
/usr/share/doc/bacula-common/ReleaseNotes.gz, presumably from
upstream. Buried toward the bottom are several statements that the
1.36 and 1.38 database formats differ.
-----------------------------
Major Changes in 1.38:
...
- There is a new database format that is not compatible
with previous databases. You must upgrade if converting
from 1.36.x. No changes from version 1.37.30.
---------------------------------------
That and some other items (e.g., daemons are not compatible with earlier
versions) seem worth flagging for News.Debian to show to all
upgraders.
I suspect similar issues are present with other database backends as
well.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages bacula-director-pgsql depends on:
ii bacula-director-common 1.38.9-10 Network backup, recovery and verif
ii dbconfig-common 1.8.13 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii postgresql-client 7.5.19 front-end programs for PostgreSQL
ii postgresql-client-8.1 8.1.4-1 front-end programs for PostgreSQL
Versions of packages bacula-director-pgsql recommends:
ii postgresql 7.5.19 object-relational SQL database man
ii postgresql-8.1 8.1.4-1 object-relational SQL database, ve
-- 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/create_tables: false
bacula-director-pgsql/purge: false
* bacula-director-pgsql/pgsql_root_username: postgres
bacula-director-pgsql/pgsql/method: unix socket
bacula-director-pgsql/db/app-user:
bacula-director-pgsql/db/dbname: ${pkg}
bacula-director-pgsql/remote/host:
bacula-director-pgsql/pgsql/admin-user: postgres
bacula-director-pgsql/database-type:
bacula-director-pgsql/remote/port:
* bacula-director-pgsql/remove_catalog_on_purge: false
bacula-director-pgsql/drop_db: false
bacula-director-pgsql/remote/newhost:
bacula-director-pgsql/performing_upgrade: false
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/import-oldsettings:
* bacula-director-pgsql/db_host: localhost
bacula-director-pgsql/pgsql/manualconf:
* bacula-director-pgsql/dbconfig-install: false
bacula-director-pgsql/dbconfig-upgrade: true
bacula-director-pgsql/db_user: bacula
bacula-director-pgsql/dbconfig-remove: true
bacula-director-pgsql/upgrade-error: abort
bacula-director-pgsql/pgsql/changeconf: false
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
