package mysql-server-5.7 5.7.23-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
?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.23-
ProcVersionSign
Uname: Linux 4.4.0-135-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Sep 13 14:05:02 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-01-31 (592 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Logs.var.
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.4
apt 1.2.27
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.23-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
From your Log: alternatives: warning: forcing reinstallation of alternative /etc/mysql/ mysql.cnf because link group my.cnf is broken alternatives: warning: not replacing /etc/mysql/my.cnf with a link
update-
update-
Renaming removed key_buffer and myisam-recover options (if present)
ERROR: Unable to start MySQL server:
mysqld: [ERROR] Found option without preceding group in config file /etc/mysql/my.cnf at line 1!
mysqld: [ERROR] Fatal error in defaults handling. Program aborted!
I can't see from the report what exactly happened before, but it seems your local configuration for mysql is broken and that renders the system unable update the package.
You'll have to fix your configuration by either replacing it with the working default config or repairing whatever was done wrong.
Then the upgrade will work again.
If you don#t actually use mysql and wonder why this shows up at all you might remove it (and check which dependencies would be removed with it) and consider that a "fix" to the config as well.