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

Bug #1901995 reported by masson
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

impossible d'installer mysql-server depuis le passage a 20.10

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: mysql-server-8.0 8.0.22-0ubuntu0.20.10.2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct 27 20:13:02 2020
DpkgHistoryLog:
 Start-Date: 2020-10-27 20:02:58
 Requested-By: djimel (1000)
 Install: libevent-pthreads-2.1-7:amd64 (2.1.12-stable-1, automatic)
 Upgrade: mysql-client-8.0:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), mysql-server:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), mysql-server-8.0:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), mysql-client-core-8.0:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), libmysqlclient21:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), libmysqlclient21:i386 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2), mysql-server-core-8.0:amd64 (8.0.21-1, 8.0.22-0ubuntu0.20.10.2)
 Remove: libc++1:amd64 (1:10.0-50~exp1), libc++1-10:amd64 (1:10.0.1-6), discord:amd64 (0.0.10)
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-09-04 (785 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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
MySQLVarLibDirListing: ['binlog.000058', 'binlog.000052', 'sys', 'binlog.000063', 'binlog.000059', 'binlog.000055', 'server-key.pem', 'mysql.ibd', '#ib_16384_0.dblwr', 'ib_logfile1', 'performance_schema', 'ib_logfile0', 'ibtmp1', 'binlog.000060', 'binlog.000056', '#innodb_temp', 'auto.cnf', 'binlog.000053', 'debian-5.7.flag', 'binlog.000057', 'ca-key.pem', 'djimel50.pid', 'binlog.000066', 'client-cert.pem', 'binlog.000064', 'binlog.000065', 'client-key.pem', '#ib_16384_1.dblwr', 'ibdata1', 'binlog.000062', 'mysql_upgrade_info', 'undo_002', 'ca.pem', 'undo_001', 'binlog.index', 'binlog.000061', 'binlog.000054', 'server-cert.pem', 'ib_buffer_pool', 'mysql', 'public_key.pem', 'private_key.pem']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=e29e41ee-8a8c-4ada-ab4c-96c9e856e51c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt 2.1.10
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.10.2 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)

Revision history for this message
masson (jeanmi50) wrote :
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.

Based on the logs, it seems like you were trying to upgrade the mysql version from 8.0.21-1 to 8.0.22-0ubuntu0.20.10.2. It also seems like this bug is related to LP #1901708, but what I found interesting is that the time it for the "Server upgrade" operation to complete was less than the timeout:

2020-10-27T19:07:11.091558Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' started.
2020-10-27T19:11:45.104517Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' completed.

I would like to request more information from you before we can proceed with the analysis. Could you please inform whether you have a large MySQL database, or whether the system load was high during the upgrade process? I would also like to know when the bug manifested: was it on 2020-10-27T19:07:11, or did it happen later?

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
Launchpad Janitor (janitor) wrote :

[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-8.0 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers