package mysql-server-8.0 8.0.22-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-8.0 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
It's coming up again and again.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.22-
ProcVersionSign
Uname: Linux 5.4.0-54-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
AptOrdering:
mysql-
mysql-
mysql-
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckR
Date: Tue Dec 1 10:55:45 2020
DpkgHistoryLog:
Start-Date: 2020-12-01 10:54:00
Commandline: /usr/bin/
Upgrade: mysql-client-
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-11-28 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.22-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to file a bug report.
From your logs, I can see the following error message:
[ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
The code "11" means that the resource is temporarily unavailable. From my recollection, this error can mean that there is another instance of MySQL running, perhaps in an inconsistent state. You can try verifying whether this is true with the following command:
lsof -i:3306
If you see that there is indeed a dangling MySQL process running, you can either attempt to kill it by hand, or reboot your system.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://