package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1708284 reported by shaoen on 2017-08-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)

Bug Description

This happened while upgrading from 14.04 LTS to 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.19-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Aug 2 13:52:30 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-06-15 (779 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['msData', 'pr', 'ib_logfile1', 'performance_schema', 'mysql', 'mainDb', 'debian-5.7.flag', 'ibdata1', 'ib_logfile0', 'mysql_upgrade_info', 'debian-5.5.flag']
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-77-generic root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.19-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-08-02 (0 days ago)

shaoen (shaoen) wrote :


From your log:
2017-08-02T20:55:29.260507Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2017-08-02T20:55:29.260530Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.

But more concering:
mysql start/running, process 26743^M
Checking if update is needed.^M
Checking server version.^M
Error: Server version (5.5.54-0ubuntu0.14.04.1) does not match with the version of^M
the server (5.7.19) with which this program was built/distributed. You can^M
use --skip-version-check to skip this check.^M
mysql_upgrade failed with exit status 3^

This seems like an extra out-of-archive mysql running locally and some config around it that breaks your re-start of the service and thereby the upgrade.

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here:

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers