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

Bug #1904272 reported by Anant Pratap Singh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
New
Undecided
Unassigned

Bug Description

buo

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.22-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
AptOrdering:
 mysql-client-8.0:amd64: Install
 libevent-pthreads-2.1-7:amd64: Install
 mysql-server-8.0:amd64: Install
 mysql-server-core-8.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Nov 7 17:25:28 2020
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-09-25 (416 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
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: ['public_key.pem', 'ca.pem', 'ib_logfile0', 'performance_schema', 'ib_buffer_pool', 'binlog.000007', 'undo_002', 'debian-5.7.flag', 'binlog.000011', 'binlog.000008', 'client-cert.pem', 'ib_logfile1', 'binlog.000010', 'client-key.pem', 'ibdata1', '#ib_16384_0.dblwr', 'binlog.000003', 'binlog.000004', 'mysql_upgrade_info', 'auto.cnf', 'mysql.ibd', 'binlog.000001', 'undo_001', 'binlog.000006', 'ca-key.pem', 'binlog.000012', 'binlog.000002', 'binlog.000009', 'private_key.pem', 'mysql', 'sys', 'binlog.000005', '#innodb_temp', 'server-key.pem', 'binlog.index', 'server-cert.pem', '#ib_16384_1.dblwr']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=64f9e1a1-6009-481a-981c-c0ae492fe5fb ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.22-0ubuntu0.20.04.2 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-10-17 (27 days ago)

Revision history for this message
Anant Pratap Singh (anantsinghh) wrote :
Revision history for this message
Avital Ostromich (avital) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
affects: ubuntu → mysql-8.0 (Ubuntu)
tags: removed: need-duplicate-check
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thanks for taking the time to report this bug and make Ubuntu better.

By looking at the logs, it seems to me like this bug is a duplicate of LP #1901708. The following excerpt is what made me reach this conclusion:

2020-11-07T11:45:24.850554Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' started.
2020-11-07T11:53:43.204161Z 4 [System] [MY-013381] [Server] Server upgrade from '80021' to '80022' completed.

As you can see, the "Server upgrade" step took almost 10 minutes to complete, which may have triggered a timeout the package has in place. We are currently investigating why this operation is taking such a long time to complete, but we still haven't found the root cause. You can try working around this issue by running "apt-get install mysql-server" again; it should succeed now.

If you don't think this bug is a duplicate of LP #1901708, or if you have more information you can provide that would help us diagnose the issue, please leave a comment and we will be happy to follow up on it.

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers