package mysql-server-5.7 5.7.20-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
package mysql-server-5.7 5.7.20-
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.20-
ProcVersionSign
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
unity-tweak-tool: Install
mysql-server-5.7: Configure
mysql-server: Configure
unity-tweak-tool: Configure
NULL: ConfigurePending
Architecture: amd64
Date: Thu Dec 7 10:44:45 2017
DuplicateSignature:
package:
Setting up mysql-server-5.7 (5.7.20-
dpkg: error processing package mysql-server-5.7 (--configure):
subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-07-07 (152 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Logs.var.
MySQLConf.
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.20-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Hi Reza,
the service needs to restart on an upgrade to pick up the changes but that fails for you.
From your log: 07T03:44: 45.016818Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 07T03:44: 45.016860Z 0 [Note] InnoDB: Unable to open the first data file 07T03:44: 45.016895Z 0 [ERROR] InnoDB: Operating system error number 11 in a file operation. 07T03:44: 45.016921Z 0 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable' 07T03:44: 45.016938Z 0 [Note] InnoDB: Some operating system error numbers are described at http:// dev.mysql. com/doc/ refman/ 5.7/en/ operating- system- error-codes. html 07T03:44: 45.016966Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1' 07T03:44: 45.016988Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_ data_file_ path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 07T03:44: 45.017007Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2017-12-
2017-12-
2017-12-
2017-12-
2017-12-
2017-12-
2017-12-
2017-12-
That either means you have another mysql running (e.g. manual setup in a different dir) or that your shutdown of the service was really unclean.
[1] holds a similar discussion and hints how to resolve.
[1]: https:/ /serverfault. com/questions/ 477448/ mysql-keeps- crashing- innodb- unable- to-lock- ibdata1- error-11