package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Probably relates to LP: #1612517
Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial).
I'm not sure from which version the config originates. After the option to send this report, I also saw this message in the terminal:
Setting up mysql-server-5.7 (5.7.15-
Renaming removed key_buffer and myisam-recover options (if present)
ERROR: Unable to start MySQL server:
2016-10-
2016-10-
After removing the opposing statement from /etc/mysql/my.cnf (and starting apt-get -f install) the upgrade continued successfully (DB and tables upgraded and DB started) and the server restarted OK.
JFYI
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.15-
ProcVersionSign
Uname: Linux 3.13.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Oct 18 15:54:05 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Logs.var.
Logs.var.
MySQLConf.
MySQLConf.
[mysqld_safe]
syslog
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.15-
UpgradeStatus: Upgraded to xenial on 2016-10-18 (0 days ago)
description: | updated |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
> After removing the opposing statement from /etc/mysql/my.cnf
> (and starting apt-get -f install) the upgrade continued
> successfully (DB and tables upgraded and DB started) and the
> server restarted OK.
Awesome! As you discovered mysql's variable/ settings/ configuration names have changed over the years and upgrading from 5.5 to 5.7 exposed that. The fix is exactly as you describe, needing to update your configuration.
> JFYI
Thanks!