package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

Bug #1849694 reported by Brian Kushner
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

not sure

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: mysql-server-8.0 8.0.17-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Thu Oct 24 10:31:13 2019
ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-10-13 (741 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt 1.9.4
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago)

Revision history for this message
Brian Kushner (bkushner) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi Brian,
from your log:
mysqld will log errors to /var/log/mysql/error.log
2019-10-24T14:30:52.608720Z 0 [ERROR] [MY-010946] [Server] Failed to start mysqld daemon. Check mysqld error log.
Warning: Unable to start the server.
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.

And if we check said error log:
2019-10-24T15:17:00.139004Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-10-24T15:17:01.204165Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17-0ubuntu2) (Ubuntu).
2019-10-24T15:17:01.978668Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2019-10-24T15:17:01.981218Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17-0ubuntu2) starting as process 3984
2019-10-24T15:17:04.278931Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-10-24T15:17:04.285654Z 0 [ERROR] [MY-000067] [Server] unknown variable 'query_cache_limit=1M'.

Now that points to 'query_cache_limit=1M' being in your config but not (or no more) being supported.
And [1] confirms this.
Default configurations are upgraded, but yours seems to be customized, so you'd need to adapt your local configuration to be able to work with the newer version of mysql - then you will be able to restart the service and that will also allow the upgrade to proceed.

[1]: https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_query_cache_limit

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

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