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

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

Bug Description

I cannot complete the mysql server install!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.18-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 libmysqlclient-dev: Install
 mysql-server-5.7: Configure
 mysql-server: Configure
 libmysqlclient-dev: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sun May 14 08:33:31 2017
DuplicateSignature:
 package:mysql-server-5.7:5.7.18-0ubuntu0.16.04.1
 Setting up mysql-server-5.7 (5.7.18-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 2016-08-24 (262 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
KernLog:

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: ['sys', 'chat_app_test', 'ib_buffer_pool', 'ibdata1', 'chat_app_production', 'chat_app_development', 'ib_logfile1', 'ibtmp1', 'performance_schema', 'chat_development', 'debian-5.7.flag', 'wurfare_development', 'chat_production', 'wurfare_test', 'ib_logfile0', 'auto.cnf', 'mysql', 'mysql_upgrade_info', 'chat_test']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=64ac890a-ddba-45af-9089-51b6f163fec0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.18-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
Radu Dinca (radudinca) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Radu,

From the log:
2017-05-14T05:23:20.224070Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2017-05-14T05:23:20.224086Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-05-14T05:23:20.224089Z 0 [Note] InnoDB: Retrying to lock the first data file

Is there anything running already in the paths the package would use.
An older manually installed .deb a third party mysql or anything like it?

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.