Ubuntu
mysql-5.7 package

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

Bug #1802456 reported by aji
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Happens while updating mysql.
Error while updating:

Setting up mysql-server-5.7 (5.7.24-0ubuntu0.18.04.1) ...
Cannot stat file /proc/3163/fd/1023: Permission denied
Cannot stat file /proc/3351/fd/5: Permission denied
Cannot stat file /proc/3351/fd/6: Permission denied
Cannot stat file /proc/3351/fd/7: Permission denied
Cannot stat file /proc/3351/fd/8: Permission denied
Cannot stat file /proc/3351/fd/9: Permission denied
Cannot stat file /proc/3351/fd/10: Permission denied
Cannot stat file /proc/3351/fd/11: Permission denied
Cannot stat file /proc/3351/fd/64: Permission denied
Cannot stat file /proc/3351/fd/70: Permission denied
Cannot stat file /proc/3351/fd/1023: Permission denied
Cannot stat file /proc/3370/fd/6: Permission denied
Cannot stat file /proc/3370/fd/7: Permission denied
Cannot stat file /proc/3370/fd/8: Permission denied
Cannot stat file /proc/3370/fd/9: Permission denied
Cannot stat file /proc/3370/fd/10: Permission denied
Cannot stat file /proc/3370/fd/11: Permission denied
Cannot stat file /proc/3370/fd/12: Permission denied
Cannot stat file /proc/3385/fd/4: Permission denied
Cannot stat file /proc/3385/fd/6: Permission denied
Cannot stat file /proc/3385/fd/7: Permission denied
Cannot stat file /proc/3385/fd/8: Permission denied
Cannot stat file /proc/3385/fd/9: Permission denied
Cannot stat file /proc/3403/fd/6: Permission denied
Cannot stat file /proc/3403/fd/7: Permission denied
Cannot stat file /proc/3403/fd/8: Permission denied
Cannot stat file /proc/3403/fd/9: Permission denied
Cannot stat file /proc/3403/fd/10: Permission denied
Cannot stat file /proc/3403/fd/11: Permission denied
Cannot stat file /proc/3403/fd/12: Permission denied
Cannot stat file /proc/3403/fd/16: Permission denied
Cannot stat file /proc/3403/fd/17: Permission denied
Checking if update is needed.
This installation of MySQL is already upgraded to 5.7.24, use --force if you still need to run mysql_upgrade
Cannot stat file /proc/3163/fd/1023: Permission denied
Cannot stat file /proc/3351/fd/5: Permission denied
Cannot stat file /proc/3351/fd/6: Permission denied
Cannot stat file /proc/3351/fd/7: Permission denied
Cannot stat file /proc/3351/fd/8: Permission denied
Cannot stat file /proc/3351/fd/9: Permission denied
Cannot stat file /proc/3351/fd/10: Permission denied
Cannot stat file /proc/3351/fd/11: Permission denied
Cannot stat file /proc/3351/fd/64: Permission denied
Cannot stat file /proc/3351/fd/70: Permission denied
Cannot stat file /proc/3351/fd/1023: Permission denied
Cannot stat file /proc/3370/fd/6: Permission denied
Cannot stat file /proc/3370/fd/7: Permission denied
Cannot stat file /proc/3370/fd/8: Permission denied
Cannot stat file /proc/3370/fd/9: Permission denied
Cannot stat file /proc/3370/fd/10: Permission denied
Cannot stat file /proc/3370/fd/11: Permission denied
Cannot stat file /proc/3370/fd/12: Permission denied
Cannot stat file /proc/3385/fd/4: Permission denied
Cannot stat file /proc/3385/fd/6: Permission denied
Cannot stat file /proc/3385/fd/7: Permission denied
Cannot stat file /proc/3385/fd/8: Permission denied
Cannot stat file /proc/3385/fd/9: Permission denied
Cannot stat file /proc/3403/fd/6: Permission denied
Cannot stat file /proc/3403/fd/7: Permission denied
Cannot stat file /proc/3403/fd/8: Permission denied
Cannot stat file /proc/3403/fd/9: Permission denied
Cannot stat file /proc/3403/fd/10: Permission denied
Cannot stat file /proc/3403/fd/11: Permission denied
Cannot stat file /proc/3403/fd/12: Permission denied
Cannot stat file /proc/3403/fd/16: Permission denied
Cannot stat file /proc/3403/fd/17: Permission denied
^Cdpkg: error processing package mysql-server-5.7 (--configure):
 installed mysql-server-5.7 package post-installation script subprocess was interrupted
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.7; however:
  Package mysql-server-5.7 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 mysql-server-5.7
 mysql-server

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.24-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Fri Nov 9 12:35:24 2018
ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-08-13 (87 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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: ['ib_logfile1', 'ib_buffer_pool', 'mysql', 'springboard_blog', 'auto.cnf', 'performance_schema', 'debian-5.7.flag', 'ibdata1', 'mysql_upgrade_info', 'sys', 'ib_logfile0', 'django_learned', 'ibtmp1']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=c25f2dc2-1698-4a64-9607-aa87a3f47d32 ro quiet splash nouveau.modeset=0 mem_sleep_default=deep nouveau.runpm=0 vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.6
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2018-11-09T11:58:28.509889

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

Hi aji,
I see in your log this:
2018-11-09T06:38:17.243476Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2018-11-09T06:38:17.243536Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2018-11-09T06:38:17.243578Z 0 [Note] InnoDB: Unable to open the first data file
2018-11-09T06:38:17.243617Z 0 [ERROR] InnoDB: Operating system error number 11 in a file operation.
2018-11-09T06:38:17.243651Z 0 [ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable'
2018-11-09T06:38:17.243679Z 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
2018-11-09T06:38:17.243705Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2018-11-09T06:38:17.243754Z 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!
2018-11-09T06:38:17.243781Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file
2018-11-09T06:38:17.845925Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2018-11-09T06:38:17.845993Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-11-09T06:38:17.846020Z 0 [ERROR] Failed to initialize builtin plugins.

That seems like either a (very) unclean stop of a former service, but more likely a second mysql already running (or mariab or others using similar file layouts).

I can't really action on that as the log is not pointing to an actual bug in Ubuntu, you'd have to check your local setup for the issue that I outlined above to get it right.

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.
Subscribing...

Other bug subscribers

Remote bug watches

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