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

Bug #1979923 reported by Sanjay
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

During upgrade mysql is not fully upgradded

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.29-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189
Uname: Linux 5.4.0-121-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 27 02:12:59 2022
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-06-04 (2213 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.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.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf'
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=daf7ae05-9396-41d4-bcbc-c049f7ca52c2 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.2
 apt 2.0.8
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.29-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2022-06-26 (0 days ago)

Revision history for this message
Sanjay (saru1683) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

Thanks for reporting this bug and trying to make Ubuntu better.

Checking the logs I found this stacktrace:

01:00:28 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x562e12ba3a30
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f850bbc9ce0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x562e0e206ad1]
/usr/sbin/mysqld(print_fatal_signal(int)+0x2fb) [0x562e0d0a77db]
/usr/sbin/mysqld(handle_fatal_signal+0xa5) [0x562e0d0a7895]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f851af84420]
/usr/sbin/mysqld(dd::sdi::store(THD*, dd::Table const*)+0xd0) [0x562e0df73350]
/usr/sbin/mysqld(dd::upgrade_57::add_sdi_info(THD*)+0xb00) [0x562e0e1d6490]
/usr/sbin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0xeda) [0x562e0e1da17a]
/usr/sbin/mysqld(+0x11f6d86) [0x562e0d16cd86]
/usr/sbin/mysqld(+0x27e1bcd) [0x562e0e757bcd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f851af78609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f851a1c8133]

As the message says this might be a hardware issue, make sure everything is working fine.

I also found multiple occurrences of this in the kernel log:

[19834.502038] audit: type=1400 audit(1656291628.048:273): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/69410/task/69411/mem" pid=69410 comm="boot" requested_mask="r" denied_mask="r" fsuid=121 ouid=121

So apparmor is denying this "open" operation which might be causing the crash. I took a look at the package changes in Focal and the apparmor rules have not been changed for a while, so I do not think this might be a regression.

Could you check some warning messages in your dmesg output and make sure there is no hardware issue?

I am setting the status of this bug to Incomplete, once you provided the requested info set it back to New and we will take a look again.

Changed in mysql-8.0 (Ubuntu):
status: New → 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

Remote bug watches

Bug watches keep track of this bug in other bug trackers.