[pkg-bacula-devel] Bug#681790: Bug#681790: /usr/sbin/bacula-dir: fails to upgrade database when database is on a remote machine

[Enrico Ghera - AZ Imballaggi S.r.l.]

On Tue, 17 Jul 2012 20:53:52 +0100, Bart Swedrowski <bart at timedout.org>
wrote:
> Package: bacula-director-mysql
> Version: 5.2.6+dfsg-1~bpo60+1
> Severity: important
> File: /usr/sbin/bacula-dir
> 
> On 16 July 2012 16:45, Enrico Ghera <enrico at azimballaggi.com> wrote:
>> * bacula-director-mysql/dbconfig-install: false
> 
> This indicates that something went wrong with dbconfig; did you use
> dbconfig originally to set up the remote database or did you install
> it locally initially and perhaps *then* moved it to remote host?
>

as far as I can remember I installed locally and then configured by hand
the remote mysql host.
my memories are misty... it was more than an year ago.
 
> Also, could you post contents of files /etc/dbconfig-common/bacula-*
> (grepping out sensitive information, naturally)
> 
# automatically generated by the maintainer scripts of
bacula-director-mysql
# any changes you make will be preserved, though your comments
# will be lost!  to change your settings you should edit this
# file and then run "dpkg-reconfigure bacula-director-mysql"

# dbc_install: configure database with dbconfig-common?
#              set to anything but "true" to opt out of assistance
dbc_install='false'

# dbc_upgrade: upgrade database with dbconfig-common?
#              set to anything but "true" to opt out of assistance
dbc_upgrade='true'

# dbc_remove: deconfigure database with dbconfig-common?
#             set to anything but "true" to opt out of assistance
dbc_remove=''

# dbc_dbtype: type of underlying database to use
#       this exists primarily to let dbconfig-common know what database
#       type to use when a package supports multiple database types.
#       don't change this value unless you know for certain that this
#       package supports multiple database types
dbc_dbtype='mysql'

# dbc_dbuser: database user
#       the name of the user who we will use to connect to the database.
dbc_dbuser='bacula'

# dbc_dbpass: database user password
#       the password to use with the above username when connecting
#       to a database, if one is required
dbc_dbpass='#############'

# dbc_dbserver: database host.
#       leave unset to use localhost (or a more efficient local method
#       if it exists).
dbc_dbserver=''

# dbc_dbport: remote database port
#       leave unset to use the default.  only applicable if you are
#       using a remote database.
dbc_dbport=''

# dbc_dbname: name of database
#       this is the name of your application's database.
dbc_dbname='bacula'

# dbc_dbadmin: name of the administrative user
#       this is the administrative user that is used to create all of the
above
dbc_dbadmin='root'

# dbc_basepath: base directory to hold database files
#       leave unset to use the default.  only applicable if you are
#       using a local (filesystem based) database.
dbc_basepath=''

##
## postgresql specific settings.  if you don't use postgresql,
## you can safely ignore all of these
##

# dbc_ssl: should we require ssl?
#       set to "true" to require that connections use ssl
dbc_ssl=''

# dbc_authmethod_admin: authentication method for admin
# dbc_authmethod_user: authentication method for dbuser
#       see the section titled "AUTHENTICATION METHODS" in
#       /usr/share/doc/dbconfig-common/README.pgsql for more info
dbc_authmethod_admin=''
dbc_authmethod_user=''

##
## end postgresql specific settings
##

there I can see the password is not the one actually in use, and the host
is not specified, assuming local.
I don't remember being asked about databases during the first
installation.
maybe it's my fault.
should I correct the content of
/etc/dbconfig-common/bacula-director-mysql.conf
to reflect the actual configuration?



> Regards,
> Bart