Your message dated Fri, 22 Feb 2013 18:15:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#700521: libdspam7-drv-mysql upgrade breaks dspam,
eradicating SQL db config parameters
has caused the Debian Bug report #700521,
regarding libdspam7-drv-mysql upgrade breaks dspam, eradicating SQL db config
parameters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
700521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700521
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libdspam7-drv-mysql
Version: 3.10.1+dfsg-8
Severity: normal
Dear Maintainer,
after upgrading libdspam7-drv-mysql on my Wheezy system with messages
Setting up libdspam7-drv-mysql (3.10.1+dfsg-8) ...
dbconfig-common: writing config to /etc/dbconfig-common/libdspam7-drv-mysql.conf
Replacing config file /etc/dspam/dspam.d/mysql.conf with new version
it turned out that dspam stopped working with errors:
Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql connect data
Feb 13 20:27:57 machine dspam[7585]: _ds_pref_load: unable to initialize tools
context
Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql connect data
Feb 13 20:27:57 machine dspam[7585]: _ds_pref_load: unable to initialize tools
context
Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql connect data
Feb 13 20:27:57 machine dspam[7585]: _ds_pref_load: unable to initialize tools
context
Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql connect data
Feb 13 20:27:57 machine dspam[7585]: Unable to initialize handle to MySQL
database
Feb 13 20:27:57 machine dspam[7585]: Unable to attach DSPAM context
Feb 13 20:27:57 machine dspam[7585]: process_message returned error -2.
delivering.
etckeeper git diff shows:
--- a/dspam/dspam.d/mysql.conf
+++ b/dspam/dspam.d/mysql.conf
@@ -6,9 +6,9 @@
#
MySQLServer /var/run/mysqld/mysqld.sock
#MySQLPort 3306
-MySQLUser <redacted>
-MySQLPass <redacted>
-MySQLDb dspam
+MySQLUser
+MySQLPass
+MySQLDb
MySQLCompress true
MySQLReconnect true
and the corresponding entries in dbconfig are:
> # dbc_dbuser: database user
> # the name of the user who we will use to connect to the database.
> dbc_dbuser=''
>
> # 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=''
>
> # dbc_dbadmin: name of the administrative user
> # this is the administrative user that is used to create all of the
> above
> dbc_dbadmin=''
It seems something is seriously broken in the upgrade scripts...
I'm not even sure what the correct solution is. I just re-added the
values to the file from which they were deleted. If it were not for
etckeeper, this would be even much larger annoyance, though.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libdspam7-drv-mysql depends on:
ii dbconfig-common 1.8.47+nmu1
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-37
ii libdspam7 3.10.1+dfsg-8
ii libmysqlclient18 5.5.28+dfsg-1
ii mysql-client 5.5.28+dfsg-1
ii mysql-client-5.5 [mysql-client] 5.5.28+dfsg-1
ii ucf 3.0025+nmu3
Versions of packages libdspam7-drv-mysql recommends:
ii mysql-server 5.5.28+dfsg-1
libdspam7-drv-mysql suggests no packages.
-- debconf information:
libdspam7-drv-mysql/missing-db-package-error: abort
libdspam7-drv-mysql/passwords-do-not-match:
libdspam7-drv-mysql/internal/reconfiguring: false
libdspam7-drv-mysql/remote/host:
libdspam7-drv-mysql/db/app-user:
libdspam7-drv-mysql/remove-error: abort
libdspam7-drv-mysql/db/dbname:
libdspam7-drv-mysql/internal/skip-preseed: true
libdspam7-drv-mysql/mysql/method: unix socket
libdspam7-drv-mysql/database-type: mysql
libdspam7-drv-mysql/dbconfig-remove:
libdspam7-drv-mysql/remote/newhost:
libdspam7-drv-mysql/upgrade-backup: true
libdspam7-drv-mysql/mysql/admin-user: root
libdspam7-drv-mysql/install-error: abort
libdspam7-drv-mysql/remote/port:
libdspam7-drv-mysql/dbconfig-upgrade: true
libdspam7-drv-mysql/purge: false
libdspam7-drv-mysql/upgrade-error: abort
libdspam7-drv-mysql/dbconfig-reinstall: false
* libdspam7-drv-mysql/dbconfig-install: false
--- End Message ---
--- Begin Message ---
Le mercredi 13 février 2013 20:34:12, Petr Baudis a écrit :
> Package: libdspam7-drv-mysql
> Version: 3.10.1+dfsg-8
> Severity: normal
>
> Dear Maintainer,
>
> after upgrading libdspam7-drv-mysql on my Wheezy system with messages
>
> Setting up libdspam7-drv-mysql (3.10.1+dfsg-8) ...
> dbconfig-common: writing config to
> /etc/dbconfig-common/libdspam7-drv-mysql.conf Replacing config file
> /etc/dspam/dspam.d/mysql.conf with new version
>
> it turned out that dspam stopped working with errors:
>
> Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql connect data
> Feb 13 20:27:57 machine dspam[7585]: _ds_pref_load: unable to initialize
> tools context Feb 13 20:27:57 machine dspam[7585]: file : incomplete mysql
> connect data Feb 13 20:27:57 machine dspam[7585]: _ds_pref_load: unable to
> initialize tools context Feb 13 20:27:57 machine dspam[7585]: file :
> incomplete mysql connect data Feb 13 20:27:57 machine dspam[7585]:
> _ds_pref_load: unable to initialize tools context Feb 13 20:27:57 machine
> dspam[7585]: file : incomplete mysql connect data Feb 13 20:27:57 machine
> dspam[7585]: Unable to initialize handle to MySQL database Feb 13 20:27:57
> machine dspam[7585]: Unable to attach DSPAM context Feb 13 20:27:57
> machine dspam[7585]: process_message returned error -2. delivering.
>
> It seems something is seriously broken in the upgrade scripts...
Sorry about that. This only affects user upgrading libdspam-drv-{mysql,pgsql}
from a version later than the one in lenny. Hence, people from stable release
aren't affected and people installing it now won't have any problem. It would
probably have been possible to give a better upgrade path for current wheezy
users but I wanted to make the patch minimal.
>
> I'm not even sure what the correct solution is. I just re-added the
> values to the file from which they were deleted. If it were not for
> etckeeper, this would be even much larger annoyance, though.
Unfortunetely since this won't affect upgrade from lenny (which isn't even
supported anyway), I doubt I can obtain an unblock for a package with a better
upgrade path.
I'm not completely familiar with dbconfig and ucf so I don't know if there is a
way to recover the value. But since the mysql config is quite small, one
"solution" would be to just do a backup, purge and reinstall the file and then
copy back the changes.
One thing that might be considered is to add a NEWS entry to warn users about
that. Feel free to reopen the bug if you thing such thing *must* be added.
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
