Thank you for taking the time to file a bug report.
From DpkgTerminalLog.txt, it is indeed clear that the problem happens
when the postinst script attempts to kill mysqld. My initial suspicion
was that apparmor could be involved (since we're seeing a kill being
denied even when it's executed by root), so I checked your dmesg log
and:
[ 1455.760969] audit: type=1400 audit(1718130651.639:278):
apparmor="DENIED" operation="signal" class="signal"
profile="/usr/sbin/mysqld" pid=31903 comm="mysql-server-8."
requested_mask="receive" denied_mask="receive" signal=term peer="vscode"
I don't understand how you were able to kill the process afterwards,
though. Maybe there's a setup time when apparmor won't allow the
process to receive a kill signal, and the postinst script was unlucky to
be executed during this time frame?
Are you able to reproduce the issue if you reinstall mysql?
I couldn't reproduce the problem here, so I'm afraid we will need more
details about your setup.
Thanks.
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069080
Title:
package mysql-server-8.0 8.0.37-0ubuntu0.24.04.1 failed to
install/upgrade: installed mysql-server-8.0 package post-installation
script subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2069080/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
