package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

Bug #1914167 reported by nicholas wayne barrett
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

update

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.23-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Feb 1 18:46:50 2021
DpkgHistoryLog:
 Start-Date: 2021-02-01 18:34:05
 Commandline: apt-get dist-upgrade
 Requested-By: defensor (1000)
 Upgrade: mysql-client-8.0:amd64 (8.0.22-0ubuntu0.20.04.3, 8.0.23-0ubuntu0.20.04.1), mysql-server-8.0:amd64 (8.0.22-0ubuntu0.20.04.3, 8.0.23-0ubuntu0.20.04.1), mysql-client-core-8.0:amd64 (8.0.22-0ubuntu0.20.04.3, 8.0.23-0ubuntu0.20.04.1), firefox-locale-en:amd64 (84.0.2+build1-0ubuntu0.20.04.1, 85.0+build1-0ubuntu0.20.04.1), libmysqlclient21:amd64 (8.0.22-0ubuntu0.20.04.3, 8.0.23-0ubuntu0.20.04.1), firefox:amd64 (84.0.2+build1-0ubuntu0.20.04.1, 85.0+build1-0ubuntu0.20.04.1), mysql-server-core-8.0:amd64 (8.0.22-0ubuntu0.20.04.3, 8.0.23-0ubuntu0.20.04.1)
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-03-28 (311 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
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', 'public_key.pem', 'binlog.000184', 'server-key.pem', 'binlog.000192', 'binlog.000190', '#innodb_temp', 'mysql.ibd', '#ib_16384_1.dblwr', 'binlog.000183', 'private_key.pem', 'ib_logfile0', '#ib_16384_0.dblwr', 'client-cert.pem', 'binlog.000195', 'undo_001', 'binlog.000185', 'binlog.000188', 'binlog.000187', 'client-key.pem', 'binlog.000197', 'binlog.000198', 'undo_002', 'mysql', 'binlog.000191', 'debian-5.7.flag', 'mysql_upgrade_info', 'binlog.000194', 'binlog.000189', 'ca.pem', 'ib_buffer_pool', 'ca-key.pem', 'binlog.index', 'server-cert.pem', 'binlog.000193', 'auto.cnf', 'sys', 'ibdata1', 'binlog.000186', 'performance_schema', 'binlog.000196']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=1c982f38-8e12-47df-89bf-7eddfe8b731c ro quiet splash vt.handoff=7
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
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.4
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

== Error Log ==
2021-02-02T00:35:33.002528Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx reported: 'Preparation of I/O interfaces failed, X Protocol won't be accessible'
2021-02-02T00:35:33.003104Z 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'

Revision history for this message
nicholas wayne barrett (abulijahpisces) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you for taking the time to file a bug report.

Unfortunately, I am unable to reproduce it locally using a Focal container with the latest MySQL package installed. I could not find anything particularly wrong in your configuration files either, and, although your Logs.var.log.mysql.error.log.txt contains a few errors, they are not responsible for the problem you are experiencing.

We do have similar bugs reported against MySQL which contain a similar pattern found in your logs:

2021-02-02T00:38:01.105311Z 4 [System] [MY-013381] [Server] Server upgrade from '80022' to '80023' started.
2021-02-02T00:45:15.751998Z 4 [System] [MY-013381] [Server] Server upgrade from '80022' to '80023' completed.

The "Server upgrade" step is taking almost 8 minutes to complete, which can cause a problem with systemd's timeout (IIRC, it's set to 5 minutes by default). I'm not sure that you are experiencing same problem, though.

I would like to request a bit more information from you before we can proceed from the investigation. Could you post the contents of:

$ journalctl -u mysql.service

please? This will probably contain systemd-specific messages that might help us diagnose what's going on.

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

Changed in mysql-8.0 (Ubuntu):
status: New → Incomplete
Bryce Harrington (bryce)
description: updated
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.