Unattended-upgrade failed to restart mysql service (due to timeout?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-8.0 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
package mysql-server-8.0 8.0.25-
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.25-
ProcVersionSign
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Sat May 22 19:08:08 2021
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2020-05-08 (379 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Logs.var.
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.5
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.25-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
summary: |
- package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to - install/upgrade: installed mysql-server-8.0 package post-installation - script subprocess returned error exit status 1 + Unattended-upgrade failed to restart mysql service (due to timeout?) |
2021-05- 23T00:04: 43.500232Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.25- 0ubuntu0. 20.04.1) . 23T00:08: 08.272503Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.25- 0ubuntu0. 20.04.1) (Ubuntu).
2021-05-
It looks like the upgrade process tried to stop the old service and start the new one, but complains that the old one didn't stop properly. Yet from the logs it appears it did stop, but took a few minutes to do it. Perhaps this was longer than the allowed timeout?
It's unclear why it took this long in this case; the log shows two shutdowns the previous day that took just a few seconds. Is it possible the system was under unusually high load? Or any other ideas why the database shutdown needed 4 minutes to complete?