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

Bug #1736873 reported by Reza Mauliadi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

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

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.20-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
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:mysql-server-5.7:5.7.20-0ubuntu0.16.04.1
 Setting up mysql-server-5.7 (5.7.20-0ubuntu0.16.04.1) ...
 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.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['mysql', 'performance_schema', 'bukalapak_development', 'ib_logfile0', 'bukalapak_test', 'debian-5.7.flag', 'auto.cnf', 'mysql_upgrade_info', 'sys', 'ibdata1', 'ib_logfile1', 'ibtmp1', 'ib_buffer_pool']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=13a9f418-a350-4e56-8d58-bb5736adf539 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.15ubuntu0.2
SourcePackage: mysql-5.7
Title: 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
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Reza Mauliadi (rezamauliadi) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Reza,
the service needs to restart on an upgrade to pick up the changes but that fails for you.

From your log:
2017-12-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.
2017-12-07T03:44:45.016860Z 0 [Note] InnoDB: Unable to open the first data file
2017-12-07T03:44:45.016895Z 0 [ERROR] InnoDB: Operating system error number 11 in a file operation.
2017-12-07T03:44:45.016921Z 0 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable'
2017-12-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
2017-12-07T03:44:45.016966Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2017-12-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!
2017-12-07T03:44:45.017007Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file

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

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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

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: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. 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
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.