| 2016-04-18 22:20:58 |
Joel Parke |
bug |
|
|
added bug |
| 2016-04-21 10:32:55 |
Robie Basak |
description |
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-04-21 10:33:06 |
Robie Basak |
summary |
package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 |
mysql fails to start after upgrade if previous defaults were customised |
|
| 2016-04-21 10:33:10 |
Robie Basak |
mysql-5.7 (Ubuntu): status |
New |
Triaged |
|
| 2016-04-21 10:33:14 |
Robie Basak |
mysql-5.7 (Ubuntu): importance |
Undecided |
High |
|
| 2016-04-21 12:45:19 |
Robie Basak |
description |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-04-22 06:26:39 |
Mathew Hodson |
tags |
amd64 apport-package xenial |
amd64 apport-package dist-upgrade xenial |
|
| 2016-04-22 06:27:40 |
Mathew Hodson |
bug task added |
|
ubuntu-release-notes |
|
| 2016-04-22 06:27:48 |
Mathew Hodson |
ubuntu-release-notes: status |
New |
Fix Released |
|
| 2016-04-22 12:20:37 |
Stein Rune Risa |
mysql-5.7 (Ubuntu): status |
Triaged |
Fix Released |
|
| 2016-04-23 21:25:15 |
Mathew Hodson |
mysql-5.7 (Ubuntu): status |
Fix Released |
Triaged |
|
| 2016-04-24 15:40:02 |
Václav Haisman |
bug |
|
|
added subscriber Václav Haisman |
| 2016-04-25 14:04:05 |
Robie Basak |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-04-25 14:04:05 |
Robie Basak |
bug task added |
|
mysql-5.7 (Ubuntu Xenial) |
|
| 2016-04-25 14:04:22 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-04-25 14:04:22 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): status |
New |
Triaged |
|
| 2016-04-26 08:31:48 |
jasonz |
bug |
|
|
added subscriber jasonz |
| 2016-04-26 14:02:25 |
Axel Pospischil |
bug |
|
|
added subscriber Axel Pospischil |
| 2016-04-26 15:13:28 |
Danny Colin |
bug |
|
|
added subscriber Danny Colin |
| 2016-04-27 12:32:58 |
jfath |
bug |
|
|
added subscriber jfath |
| 2016-04-28 19:35:21 |
Petr Malik |
bug |
|
|
added subscriber Petr Malik |
| 2016-04-29 07:24:06 |
Yufei |
bug |
|
|
added subscriber Yufei |
| 2016-04-29 10:39:25 |
Robie Basak |
mysql-5.7 (Ubuntu): assignee |
|
Lars Tangvald (lars-tangvald) |
|
| 2016-04-29 10:39:46 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): assignee |
|
Lars Tangvald (lars-tangvald) |
|
| 2016-04-29 10:39:54 |
Robie Basak |
mysql-5.7 (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-04-29 12:03:24 |
Robie Basak |
mysql-5.7 (Ubuntu): milestone |
|
ubuntu-16.05 |
|
| 2016-06-21 17:48:36 |
Jeton Thaci |
bug |
|
|
added subscriber Jeton Thaci |
| 2016-06-21 17:48:43 |
Jeton Thaci |
removed subscriber Jeton Thaci |
|
|
|
| 2016-07-12 16:52:30 |
Robie Basak |
mysql-5.7 (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2016-07-13 14:11:57 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2016-07-13 14:12:00 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): assignee |
Lars Tangvald (lars-tangvald) |
Robie Basak (racb) |
|
| 2016-07-13 14:23:10 |
Launchpad Janitor |
mysql-5.7 (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2016-07-14 11:21:09 |
Robie Basak |
mysql-5.7 (Ubuntu Xenial): milestone |
|
ubuntu-16.04.1 |
|
| 2016-07-14 11:40:06 |
Lars Tangvald |
description |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and change the value of key_buffer
3. Upgrade distro to Xenial
3. Verify that upgrade of MySQL succeeds
4. Verify that in /etc/mysql/my.cnf, key_buffer and myisam-recover are renamed, with a comment about why it was done
Alternately, install mysql-server in Xenial/Yakkety, then remove it and
change key_buffer_size and/or myisam_recover_options to key_buffer and myisam_recover in /etc/mysql/mysql.conf.d/mysqld.conf
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-07-14 11:45:46 |
Lars Tangvald |
description |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and change the value of key_buffer
3. Upgrade distro to Xenial
3. Verify that upgrade of MySQL succeeds
4. Verify that in /etc/mysql/my.cnf, key_buffer and myisam-recover are renamed, with a comment about why it was done
Alternately, install mysql-server in Xenial/Yakkety, then remove it and
change key_buffer_size and/or myisam_recover_options to key_buffer and myisam_recover in /etc/mysql/mysql.conf.d/mysqld.conf
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and save it (can just add a comment)
3. Upgrade distro to Xenial
Expected behavior:
Server upgrades and starts normally
Actual behavior:
Server fails to upgrade, because it can't start, throwing an error about 'unknown option key_buffer'
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-07-14 12:10:29 |
Robie Basak |
description |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and save it (can just add a comment)
3. Upgrade distro to Xenial
Expected behavior:
Server upgrades and starts normally
Actual behavior:
Server fails to upgrade, because it can't start, throwing an error about 'unknown option key_buffer'
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and save it (can just add a comment)
3. Upgrade distro to Xenial
Expected behavior:
Server upgrades and starts normally
Actual behavior:
Server fails to upgrade, because it can't start, throwing an error about 'unknown option key_buffer'
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/99local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-07-14 12:15:14 |
Robie Basak |
description |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and save it (can just add a comment)
3. Upgrade distro to Xenial
Expected behavior:
Server upgrades and starts normally
Actual behavior:
Server fails to upgrade, because it can't start, throwing an error about 'unknown option key_buffer'
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/99local.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped with options "key-buffer" and "myisam-recover". In 5.7, these option names have been removed and replaced with "key-buffer-size" and "myisam-recover-options" instead. If a user customised /etc/mysql/my.cnf before, then the entire file is preserved, including the removed options, causing mysqld to fail to start after upgrade to 5.7 (eg. when upgrading to 16.04).
[Impact]
Server will fail to start, causing upgrade/installation of MySQL to fail.
[Test case]
1. Install mysql-server in Ubuntu Trusty
2. Edit /etc/mysql/my.cnf and save it (can just add a comment)
3. Upgrade distro to Xenial
Expected behavior:
Server upgrades and starts normally
Actual behavior:
Server fails to upgrade, because it can't start, throwing an error about 'unknown option key_buffer'
[Regression Potential]
* If the sed command is faulty in some way it could mangle the options,
leading to the server not starting and installation failing
[Workarounds]
If your customisations were made in 15.04 or 15.10 and /etc/mysql/my.cnf.migrated does not exist, then the workarounds below are still essentially the same but with a couple of exceptions:
1. Instead of editing /etc/mysql/my.cnf.migrated, edit the file you originally changed directly. This may be /etc/mysql/my.cnf (through the symlink), or a file you changed or added in either /etc/mysql/conf.d/ or /etc/mysql/mysql.conf.d/. The command "grep -Er 'key.buffer|myisam.recover' /etc/mysql" may help you in locating this.
2. No need to run update-alternatives to remove use of /etc/mysql/my.cnf.migrated.
[Workaround Option 1/3]
To reset your MySQL configuration back to defaults, type "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" after the upgrade. Then use "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
This option is not available if /etc/mysql/my.cnf.migrated doesn't exist on your system, for example if your customisations were made on 15.04 or 15.10.
[Workaround Option 2/3]
For a quick fix while retaining your existing customised configuration, edit the [mysqld] section /etc/mysql/my.cnf.migrated as follows. But see the caveats detailed below and consider Workaround Option 3/3 instead first.
1. Replace "key_buffer" with "key_buffer_size". Note that there is a second occurrance of "key_buffer" under the [isamchk] section at the end of the file; changing this second occurrance is not necessary.
2. Replace "myisam-recover" with "myisam-recover-options".
Then use "sudo service mysql start" to start the MySQL daemon again and "sudo apt-get -f install" to recover your system packaging state.
However, this workaround does not put you in the best place for future upgrades, since packaging will continue to not be able to perfectly update this file while preserving your modifications. Additionally there may be parts of your previously customised configuration that still will not work with MySQL 5.7.
To make future upgrades smoother in the future, consider following the next workaround option instead.
[Workaround Option 3/3]
Examine /etc/mysql/my.cnf.migrated for the customisations you made previously. You can find an original version of /etc/mysql/my.cnf as shipped with 14.04 at: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/mysql-5.5/trusty/view/head:/debian/additions/my.cnf
Determine the changes you made to /etc/mysql/my.cnf. Taking only these changes and not the default contents of this file, add just your customisations into a new file at /etc/mysql/mysql.conf.d/zzlocal.cnf (preferred) and/or by editing /etc/mysql/mysql.conf.d/mysqld.cnf (to be avoided if possible) if necessary.
Run: "sudo update-alternatives --remove my.cnf /etc/mysql/my.cnf.migrated" to switch to the new configuration scheme.
Run: "sudo service mysql start" to start the MySQL daemon and "sudo apt-get -f install" to recover your system packaging state.
[Original Description]
Upgrading from 15.10 to 16.04 fails here
Not sure if this is related to a bug report already reported.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon Apr 18 18:13:33 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-04-18 (731 days ago)
InstallationMedia:
Logs.var.log.daemon.log:
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: ['debian-5.7.flag', 'debian-5.5.flag', 'debian-5.6.flag', 'ib_logfile1', 'drupal8', 'servermail', 'ib_logfile0', 'auto.cnf', 'risenlif_risenlife2', 'dynazu_wiki', 'performance_schema', 'ibdata1', 'phpmyadmin', 'ib_buffer_pool', 'mysql_upgrade_info', 'parke_wiki', 'tracker', 'mysql']
ProcCmdline: root=LABEL=DOROOT ro
RelatedPackageVersions:
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago) |
|
| 2016-07-15 19:23:49 |
Adam Conrad |
mysql-5.7 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-07-15 19:23:52 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-07-15 19:23:58 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2016-07-15 19:24:09 |
Adam Conrad |
tags |
amd64 apport-package dist-upgrade xenial |
amd64 apport-package dist-upgrade verification-needed xenial |
|
| 2016-07-18 09:13:22 |
Hristian |
bug |
|
|
added subscriber Hristian |
| 2016-07-18 09:13:26 |
Hristian |
removed subscriber Hristian |
|
|
|
| 2016-07-18 09:13:32 |
Hristian |
bug |
|
|
added subscriber Hristian |
| 2016-07-18 16:08:23 |
Francisco José Cañizares Santofimia |
bug |
|
|
added subscriber Francisco José Cañizares Santofimia |
| 2016-07-21 16:41:33 |
Launchpad Janitor |
mysql-5.7 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3424 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3459 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3477 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3486 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3501 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3518 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3521 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3588 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3614 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-3615 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5436 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5437 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5439 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5440 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5441 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5442 |
|
| 2016-07-21 16:41:33 |
Launchpad Janitor |
cve linked |
|
2016-5443 |
|
| 2016-07-21 16:53:48 |
jorge |
bug |
|
|
added subscriber jorge |
| 2016-07-21 17:02:07 |
Hauke |
bug |
|
|
added subscriber Hauke |
| 2016-07-25 03:50:54 |
Rocko |
bug |
|
|
added subscriber Rocko |
| 2016-07-26 17:22:45 |
seawolf |
bug |
|
|
added subscriber seawolf |
| 2016-08-18 13:41:40 |
takashisenko |
bug |
|
|
added subscriber takashisenko |
| 2016-10-10 16:27:01 |
Danny Colin |
removed subscriber Danny Colin |
|
|
|
| 2017-01-29 22:17:33 |
Oscar Maqueda |
bug |
|
|
added subscriber Oscar Maqueda |
| 2017-02-10 19:05:51 |
takashisenko |
removed subscriber takashisenko |
|
|
|
