Your message dated Wed, 09 Mar 2016 22:02:05 +0000 with message-id <[email protected]> and subject line Bug#811158: Removed package(s) from unstable has caused the Debian Bug report #736777, regarding mysql-server-5.5 upgrade breaks replication: Error 'You cannot 'ALTER' a log table if logging 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.) -- 736777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736777 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mysql-server-5.5 Version: 5.5.35+dfsg-0+wheezy1 Severity: important Tags: d-i Dear Maintainer, Upgrading from mysql-server-5.5.33+dfsg-0+wheezy1 to mysql-server_5.5.35+dfsg-0+wheezy1 cause replication to fail with the following error: Last_Errno: 1580 Last_Error: Error 'You cannot 'ALTER' a log table if logging is enabled' on query. Default database: 'mysql'. Query: MODIFY start_time TIMESTAMP NOT NULL,... Percona[1] and MariaDB[2] have the same issue open and have identified that the issue is caused by the lack of of the --skip-write-binlog arg to the mysql_upgrade command[3]. As stated in the linked bug reports, the workaround is to issue the following commands in MySQL: SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE; Having to issue this workaround is not desirable in a production environment when applying minor-point upgrades. The upgrade scripting should be handling this for us. [1] https://bugs.launchpad.net/percona-server/+bug/1065841 [2] https://mariadb.atlassian.net/browse/MDEV-5116 [3] https://bugs.launchpad.net/percona-server/+bug/1065841/comments/11 -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (950, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server-5.5 depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii initscripts 2.88dsf-41+deb7u1 ii libc6 2.13-38 ii libdbi-perl 1.622-1 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii lsb-base 4.1+Debian8+deb7u1 ii mysql-client-5.5 5.5.35+dfsg-0+wheezy1 ii mysql-common 5.5.35+dfsg-0+wheezy1 ii mysql-server-core-5.5 5.5.35+dfsg-0+wheezy1 ii passwd 1:4.1.5.1-1 ii perl 5.14.2-21+deb7u1 ii psmisc 22.19-1+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages mysql-server-5.5 recommends: ii heirloom-mailx [mailx] 12.5-2 ii libhtml-template-perl 2.91-1 Versions of packages mysql-server-5.5 suggests: pn tinyca <none> -- debconf information: mysql-server/error_setting_password: mysql-server-5.5/postrm_remove_databases: false mysql-server-5.5/start_on_boot: true mysql-server-5.5/nis_warning: mysql-server-5.5/really_downgrade: false mysql-server/password_mismatch: mysql-server/no_upgrade_when_using_ndb:
--- End Message ---
--- Begin Message ---Version: 5.5.46-0+deb8u1+rm Dear submitter, as the package mysql-5.5 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/811158 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
