Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#489578: bacula-director-mysql: postinstall error -- Unknown database '${db_name}'

33 views
Skip to first unread message

Teodor

unread,
Jul 30, 2008, 6:00:20 AM7/30/08
to
Package: bacula-director-mysql
Version: 2.4.1-1
Followup-For: Bug #489578

At a fresh install the postinstall script fails with:

----
Setting up bacula-director-mysql (2.4.1-1) ...
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-mysql.conf

Creating config file /etc/dbconfig-common/bacula-director-mysql.conf
with new version
granting access to database bacula for bacula@localhost: success.
verifying access for bacula@localhost: success.
creating database bacula: success.
verifying database bacula exists: success.
populating database via sql... error encountered populating database:
mysql said: ERROR 1049 (42000) at line 1: Unknown database '${db_name}'
dbconfig-common: bacula-director-mysql configure: trying again (skip
questions).
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-mysql.conf
granting access to database bacula for bacula@localhost: already exists.
creating database bacula: already exists.
populating database via sql... error encountered populating database:
dbconfig-common: writing config to
/etc/dbconfig-common/bacula-director-mysql.conf
granting access to database bacula for bacula@localhost: already exists.
creating database bacula: already exists.
populating database via sql... error encountered populating database:
mysql said: ERROR 1049 (42000) at line 1: Unknown database '${db_name}'
dbconfig-common: bacula-director-mysql configure: ignoring errors from
here forwards
done.
dbconfig-common: flushing administrative password
dbconfig-common: bacula-director-mysql configure: ignoring errors from
here forwards
dbconfig-common: bacula-director-mysql configure: ignoring errors from
here forwards
Processing configuration ...Ok.
Starting Bacula Director: bacula-dir.
----

The database 'bacula' was created, but the tables were not. I've fixed
this by commenting the "Use.. " line in
/usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql.
This is an workarround, NOT a real fix.

Although the final freeze for lenny is in effect, this is an important
bug and an upload with only with a fix for this will be allowed as a
freeze exception.

Thanks


-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-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-mysql depends on:
ii bacula-director-common 2.4.1-1 network backup, recovery and verif
ii dbconfig-common 1.8.39 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libgcc1 1:4.3.1-2 GCC support library
ii libmysqlclient15off 5.0.51a-9+lenny2 MySQL database client library
ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3
ii libwrap0 7.6.q-15 Wietse Venema's TCP wrappers libra
ii mysql-client 5.0.51a-9+lenny2 MySQL database client (meta packag
ii mysql-client-5.0 [mysq 5.0.51a-9+lenny2 MySQL database client binaries
ii python2.5 2.5.2-6 An interactive high-level object-o
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages bacula-director-mysql recommends:
ii mysql-server 5.0.51a-9+lenny2 MySQL database server (meta packag
ii mysql-server-5.0 [mysql 5.0.51a-9+lenny2 MySQL database server binaries

bacula-director-mysql suggests no packages.

-- debconf information:
* bacula-director-mysql/mysql/admin-user: root
bacula-director-mysql/purge: false
bacula-director-mysql/remove-error: abort
bacula-director-mysql/internal/skip-preseed: false
* bacula-director-mysql/dbconfig-install: true
* bacula-director-mysql/db/app-user: bacula
bacula-director-mysql/upgrade-backup: true
* bacula-director-mysql/install-error: ignore
* bacula-director-mysql/db/dbname: bacula
bacula-director-mysql/remote/host:
bacula-director-mysql/upgrade-error: abort
bacula-director-mysql/remote/port:
bacula-director-mysql/passwords-do-not-match:
bacula-director-mysql/dbconfig-upgrade: true
bacula-director-mysql/missing-db-package-error: abort
bacula-director-mysql/remote/newhost:
bacula-director-mysql/database-type: mysql
* bacula-director-mysql/mysql/method: unix socket
bacula-director-mysql/internal/reconfiguring: false
bacula-director-mysql/dbconfig-reinstall: false
bacula-director-mysql/dbconfig-remove:

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Teodor

unread,
Jul 31, 2008, 5:10:14 AM7/31/08
to
Package: bacula-director-mysql
Version: 2.4.1-1
Followup-For: Bug #441995

Due to the merge of bugs this message is ignored in the report, so reposting.
Thanks


At a fresh install the postinstall script fails with:

The database 'bacula' was created, but the tables were not. I've fixed
this by commenting the "Use.. " line in
/usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql.

This is an workarround, not a real fix.

Although the final freeze for lenny is in effect, this is an important

bug and an upload with only with a fix for this will probably be allowed
as a freeze exception (severity >= important).

0 new messages