Your message dated Sun, 5 Aug 2012 20:52:08 +1000
with message-id <201208052052.08588.only...@member.fsf.org>
and subject line Done: zabbix-server-mysql: Upgrade to 2.0 fails
has caused the Debian Bug report #683727,
regarding zabbix-server-mysql: Upgrade to 2.0 fails
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 ow...@bugs.debian.org
immediately.)
--
683727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zabbix-server-mysql
Version: 1:2.0.1+dfsg-1
Severity: grave
Justification: renders package unusable
Hello,
During the recent package upgrade, Zabbix-Server was upgraded from 1.8 to 2.0
which resulted in a load of problems, probably due to issues with the DB
upgrade (the web interface is complaining about missing fields, graphs, data
etc is missing, ....
I'm currently running the /usr/share/zabbix-server-mysql/patch.sql.gz file
against my database to see if that can fix it.
- Michel
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.37-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages zabbix-server-mysql depends on:
ii adduser 3.113+nmu3
ii debconf 1.5.45
ii fping 3.2-1
ii libc6 2.13-35
ii libcurl3-gnutls 7.26.0-1
ii libiksemel3 1.2-4
ii libldap-2.4-2 2.4.31-1
ii libmysqlclient18 5.5.25a-rel27.1-277.squeeze
ii libopenipmi0 2.0.16-1.3
ii libsnmp15 5.4.3~dfsg-2.5
ii libssh2-1 1.4.2-1
ii lsb-base 4.1+Debian7
ii ucf 3.0025+nmu3
Versions of packages zabbix-server-mysql recommends:
ii percona-server-server-5.5 [mysql-server] 5.5.25a-rel27.1-277.squeeze
ii snmpd 5.4.3~dfsg-2.5
Versions of packages zabbix-server-mysql suggests:
ii logrotate 3.8.1-4
ii zabbix-frontend-php 1:2.0.1+dfsg-1
-- Configuration Files:
/etc/default/zabbix-server changed [not included]
-- debconf information:
zabbix-server-mysql/password-confirm: (password omitted)
zabbix-server-mysql/mysql/admin-pass: (password omitted)
zabbix-server-mysql/mysql/app-pass: (password omitted)
zabbix-server-mysql/app-password-confirm: (password omitted)
zabbix-server-mysql/upgrade-backup: true
zabbix-server-mysql/import-oldsettings:
zabbix-server-mysql/remote/host:
zabbix-server-mysql/dbconfig-remove:
zabbix-server-mysql/internal/skip-preseed: false
zabbix-server-mysql/remove-error: abort
* zabbix-server-mysql/server:
zabbix-server-mysql/passwords-do-not-match:
zabbix-server-mysql/missing-db-package-error: abort
zabbix-server-mysql/db/dbname: zabbix
zabbix-server-mysql/remote/newhost:
* zabbix-server-mysql/dbconfig-install: true
* zabbix-server-mysql/dbconfig-upgrade: true
zabbix-server-mysql/mysql/admin-user: root
zabbix-server-mysql/remote/port:
zabbix-server-mysql/db/app-user: zabbix
zabbix-server-mysql/database-type: mysql
zabbix-server-mysql/purge: false
zabbix-server-mysql/internal/reconfiguring: false
zabbix-server-mysql/mysql/method: unix socket
* zabbix-server-mysql/upgrade-error: retry (skip questions)
zabbix-server-mysql/dbconfig-reinstall: false
zabbix-server-mysql/install-error: retry
--- End Message ---
--- Begin Message ---
Package: zabbix-server-mysql
Dear Michel,
As we emphasised in NEWS, README and TODO files, the database upgrade
procedure is now completely manual.
In file TODO.Debian we explain number of reasons why it has been done.
In many cases automation doesn't work and now upgrade procedure is more like
what's documented by upstream.
I apologise for inconvenience.
We're considering to add debconf warning to notify about the necessary manual
upgrade intervention.
As for now I hope you'll excuse me for closing this bug.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 683...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Regards,
Dmitry.
--- End Message ---
