package mysql-server-5.7 5.7.16-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 137
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Was busy with a do-release-upgrade when this happened
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.16-
ProcVersionSign
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Wed Jan 4 07:30:22 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 137
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.15ubuntu0.2
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.16-
UpgradeStatus: Upgraded to xenial on 2017-01-04 (0 days ago)
tags: | removed: need-duplicate-check |
Hi Gary,
thank you for your report and your help to make Ubuntu better.
From the log: dpkg/info/ mysql-server- 5.7.postinst: line 16: 32700 Killed mysqld --user=mysql --init-file="$1" --socket= "$tmpdir/ mysqld. sock" --pid-file= "$tmpdir/ mysqld. pid" > /dev/null 2>&1
/var/lib/
dpkg: error processing package mysql-server-5.7 (--configure):
subprocess installed post-installation script returned error exit status 137
There are issues in the mysql error log: /bugs.mysql. com/bug. php?id= 80642) and the postinst handles that with a || true
I see that already exists "ERROR: 1050 Table 'plugin' already exists"
But that is a known issue (https:/
The code path is also used to set a PW if set via debconf (not in your upgrade case I'd think).
And finally to alter the user after auth_socket plugin is installed. bugs.mysql. com/bug. php?id= 80632 expired= 'N', account_locked='N' WHERE user='root';"
I'd assume that the code got killed while executing those:
USE mysql;"
ALTER USER 'root'@'localhost' IDENTIFIED WITH 'auth_socket';"
# Bug: http://
UPDATE user SET password_
FLUSH PRIVILEGES;"
SHUTDOWN;"
run_init_sql "$initfile" <- runs the commands above.
But the mysql log has only valid shutdowns later on.
So the question is what killed the call to mysql in your case.
I beg a pardon, do you have any other data what happened while upgrading.
Did other than that your do-release-upgrade finish and if so is mysql now properly working.
Is a new upgrade (or install --reinstall) of mysql-server-5.7 working for you now?