package mysql-server-5.7 5.7.24-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1809930 reported by Alex Taffe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Caused during do-release-upgrade between 14.04->16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.24-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-53.74~14.04.1-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Dec 27 20:29:22 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
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
MySQLVarLibDirListing: ['bin.000001', 'mysql', 'bin.000010', 'ibdata1', 'mysql_upgrade_info', 'bin.000006', 'data_swccdb', 'data_cpsflower', 'bin-log.index', 'bin.000004', 'bin.000003', 'bin.000011', 'bin.000005', 'bin.000008', 'bin.000002', 'ib_logfile0', 'debian-5.5.flag', 'ib_logfile1', 'bin.000007', 'bin.000009', 'performance_schema']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=b4d7658f-19e6-4a7c-bb3a-240f7177349e ro console=tty1 root=LABEL=DOROOT notsc clocksource=kvm-clock net.ifnames=0
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt 1.2.29
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.24-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-12-27 (0 days ago)

Revision history for this message
Alex Taffe (alex-taffe) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

This seems to be due to a misconfiguration, from your log

ERROR: Unable to start MySQL server:
2018-12-27T20:29:22.816593Z 0 [ERROR] You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation
2018-12-27T20:29:22.818643Z 0 [ERROR] Aborting
Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues.

Then if you look for that error you find e.g. the helpful askubuntu Entry:
=> https://askubuntu.com/questions/829772/mysql-failed-to-restart-on-ubuntu-16-04

I'd ask you to follow the recommendations given there to fix up your configuration, then install/upgrade of mysql should work again.

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

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or 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-5.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (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.