package mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: 已安装 mysql-server-8.0 软件包 post-installation 脚本 子进程返回错误状态 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-8.0 (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Focal |
Expired
|
Undecided
|
Unassigned |
Bug Description
sudo apt remove mysql-server
sudo apt install mysql-server
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.20-
ProcVersionSign
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckR
Date: Tue Jul 14 19:02:09 2020
ErrorMessage: 已安装 mysql-server-8.0 软件包 post-installation 脚本 子进程返回错误状态 2
InstallationDate: Installed on 2020-07-12 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.20-
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to file a bug report.
Despite the following error:
2020-07- 14T11:03: 57.070457Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/ mysqld/ mysqlx. sock' failed, can't create lock file /var/run/ mysqld/ mysqlx. sock.lock'
I was not able to find any other error. But, judging by it... looks like you possibly have a local configuration issue. Would you be able to provide a clean step-by-step reproducer for this error ?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
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".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://