During upgrade from focal to jammy, mysql does not restart automatically, but holds up upgrade with an error dialog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-server (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1)
root@ubuntu20:~# lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
2)
root@ubuntu20:~# apt-cache policy mysql-server
mysql-server:
Installed: 8.0.31-
Candidate: 8.0.31-
Version table:
8.
500 http://
500 http://
*** 8.0.31-
100 /var/lib/
8.
500 http://
3) I expect upgrade to 22 to happen as smoothly as possible
4) What happened dialogue (see below) appeared asking to restart mysql manually
When upgrading from focal (20.04.05) to jammy (22.04.01), upgrade stops midway through with the following dialogue:
┌──────
│ │
│ Failure restarting some services for GNU libc upgrade │
│ │
│ The following services could not be restarted for the GNU libc library upgrade: │
│ │
│ mysql │
│ │
│ You will need to start these manually by running 'invoke-rc.d <service> start'. │
│ │
│ <Ok> │
│ │
└──────
Logging in into another session and attempting to restart mysql while the dialogue is still up fails as well. However, it does succeeds seconds after clicking Ok.
The following shows up in journalctl -u mysql :
Dec 10 08:49:09 ubuntu20 systemd[1]: Starting MySQL Community Server...
Dec 10 08:49:09 ubuntu20 systemd[3544]: mysql.service: Failed to determine user credentials: No such process
Dec 10 08:49:09 ubuntu20 systemd[3544]: mysql.service: Failed at step USER spawning /usr/share/
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Control process exited, code=exited, status=217/USER
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Failed with result 'exit-code'.
Dec 10 08:49:09 ubuntu20 systemd[1]: Failed to start MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Dec 10 08:49:09 ubuntu20 systemd[1]: Stopped MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: Starting MySQL Community Server...
Dec 10 08:49:09 ubuntu20 systemd[3545]: mysql.service: Failed to determine user credentials: No such process
Dec 10 08:49:09 ubuntu20 systemd[3545]: mysql.service: Failed at step USER spawning /usr/share/
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Control process exited, code=exited, status=217/USER
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Failed with result 'exit-code'.
Dec 10 08:49:09 ubuntu20 systemd[1]: Failed to start MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 6.
Dec 10 08:49:09 ubuntu20 systemd[1]: Stopped MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: Starting MySQL Community Server...
Dec 10 08:49:09 ubuntu20 systemd[3546]: mysql.service: Failed to determine user credentials: No such process
Dec 10 08:49:09 ubuntu20 systemd[3546]: mysql.service: Failed at step USER spawning /usr/share/
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Control process exited, code=exited, status=217/USER
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Failed with result 'exit-code'.
Dec 10 08:49:09 ubuntu20 systemd[1]: Failed to start MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Scheduled restart job, restart counter is at 7.
Dec 10 08:49:09 ubuntu20 systemd[1]: Stopped MySQL Community Server.
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Start request repeated too quickly.
Dec 10 08:49:09 ubuntu20 systemd[1]: mysql.service: Failed with result 'exit-code'.
Dec 10 08:49:09 ubuntu20 systemd[1]: Failed to start MySQL Community Server.
Status changed to 'Confirmed' because the bug affects multiple users.