Ubuntu
mysql-8.0 package

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 #1914066 reported by Gary Caine
52
This bug affects 12 people
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

This is what the the report a problem gave me.

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Feb 1 09:19:25 2021
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-08-02 (548 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
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
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=ebdbee5a-fce1-445c-b90a-8a2045cc4880 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: Upgraded to focal on 2020-08-09 (175 days ago)

== Error Log ==

2021-02-01T15:07:13.691189Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx reported: 'Preparation of I/O interfaces failed, X Protocol won't be accessible'
2021-02-01T15:07:13.691495Z 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'

See original description
Revision history for this message
Gary Caine (skgary) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mysql-8.0 (Ubuntu):
status: New → Confirmed
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-01T15:10:24.121291Z 4 [System] [MY-013381] [Server] Server upgrade from '80022' to '80023' started.
2021-02-01T15:18:10.211863Z 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: Confirmed → Incomplete
Revision history for this message
Gary Caine (skgary) wrote :

I'm not an expert but looks like it installed successfully here's the output you asked for
-- Reboot --
Jan 31 17:06:15 gary systemd[1]: Starting MySQL Community Server...
Jan 31 17:07:16 gary systemd[1]: Started MySQL Community Server.
Jan 31 17:08:56 gary systemd[1]: Stopping MySQL Community Server...
Jan 31 17:08:59 gary systemd[1]: mysql.service: Succeeded.
Jan 31 17:08:59 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 01 07:54:04 gary systemd[1]: Starting MySQL Community Server...
Feb 01 07:57:56 gary systemd[1]: Started MySQL Community Server.
Feb 01 08:51:23 gary systemd[1]: Stopping MySQL Community Server...
Feb 01 08:51:26 gary systemd[1]: mysql.service: Succeeded.
Feb 01 08:51:26 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 01 08:53:44 gary systemd[1]: Starting MySQL Community Server...
Feb 01 08:54:44 gary systemd[1]: Started MySQL Community Server.
Feb 01 09:04:44 gary systemd[1]: Stopping MySQL Community Server...
Feb 01 09:04:46 gary systemd[1]: mysql.service: Succeeded.
Feb 01 09:04:46 gary systemd[1]: Stopped MySQL Community Server.
Feb 01 09:20:52 gary systemd[1]: Starting MySQL Community Server...
Feb 01 09:20:57 gary systemd[1]: Started MySQL Community Server.
Feb 01 17:33:44 gary systemd[1]: Stopping MySQL Community Server...
Feb 01 17:33:45 gary systemd[1]: mysql.service: Succeeded.
Feb 01 17:33:45 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 01 17:36:58 gary systemd[1]: Starting MySQL Community Server...
Feb 01 17:38:01 gary systemd[1]: Started MySQL Community Server.
Feb 01 17:41:51 gary systemd[1]: Stopping MySQL Community Server...
Feb 01 17:41:53 gary systemd[1]: mysql.service: Succeeded.
Feb 01 17:41:53 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 02 07:12:36 gary systemd[1]: Starting MySQL Community Server...
Feb 02 07:14:05 gary systemd[1]: Started MySQL Community Server.
Feb 02 09:50:28 gary systemd[1]: Stopping MySQL Community Server...
Feb 02 09:50:29 gary systemd[1]: mysql.service: Succeeded.
Feb 02 09:50:29 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 02 13:13:46 gary systemd[1]: Starting MySQL Community Server...
Feb 02 13:14:50 gary systemd[1]: Started MySQL Community Server.
Feb 02 15:30:33 gary systemd[1]: Stopping MySQL Community Server...
Feb 02 15:30:35 gary systemd[1]: mysql.service: Succeeded.
Feb 02 15:30:35 gary systemd[1]: Stopped MySQL Community Server.
-- Reboot --
Feb 03 07:14:35 gary systemd[1]: Starting MySQL Community Server...
Feb 03 07:16:09 gary systemd[1]: Started MySQL Community Server.

Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thank you for the quick reply.

Hm, I was expecting to see an entry dated as Feb 01, at around 15:20, which is the time present in the MySQL error log.

These errors are quite hard to diagnose, because they cannot be easily reproducible. However, the "workaround" we suggest is to just run "apt-get install mysql-server" again, which usually completes the installation successfully.

Revision history for this message
Gary Caine (skgary) wrote :

OK I tried that and got this
mysql-server is already the newest version (8.0.23-0ubuntu0.20.04.1).
So it seems there was no problem, but the report a problem window came up, so I reported it.

Bryce Harrington (bryce)
description: updated
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.