Ubuntu
mysql-5.7 package

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

Bug #1857214 reported by Nibin N on 2019-12-22

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mysql-5.7 (Ubuntu)	New	Undecided	Unassigned

Bug Description

pls check

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.28-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Tue Dec 10 23:07:49 2019
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-07-12 (527 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
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
MySQLVarLibDirListing: ['performance_schema', 'ib_logfile0', 'mysql_upgrade_info', 'private_key.pem', 'ib_logfile1', 'ib_buffer_pool', 'ca-key.pem', 'client-cert.pem', 'ibtmp1', 'ca.pem', 'sys', 'smart', 'ibdata1', 'mlm', 'client-key.pem', 'server-cert.pem', 'mysql', 'debian-5.7.flag', 'server-key.pem', 'auto.cnf', 'public_key.pem']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=83a452b3-c9bb-48c2-a50c-fe237542e24f ro quiet splash vt.handoff=7
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.6
apt 1.2.32
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.28-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Nibin N (nibinn) wrote on 2019-12-22:

.etc.apparmor.d.usr.sbin.mysqld.txt Edit (1.8 KiB, text/plain; charset="utf-8")
AptOrdering.txt Edit (664 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (61.3 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (1009 bytes, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.5 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (534 bytes, text/plain; charset="utf-8")
KernLog.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Logs.var.log.mysql.error.log.txt Edit (11.8 KiB, text/plain; charset="utf-8")
MySQLConf.etc.mysql.my.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.conf.d.mysqld.cnf.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2019-12-22

tags:

removed: need-duplicate-check

Revision history for this message

Chris Guiver (guiverc) wrote on 2019-12-22:

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

The message

"mysql_upgrade: [ERROR] 1881: Operation not allowed when innodb_forced_recovery > 0.
mysql_upgrade failed with exit status 5"

implies you have a READ-ONLY database to me, ie. database issues that need correcting, OR needs a config setting reversed, in order for the upgrade to occur. It aborted to prevent database corruption (or changing settings you have put on your databases).

(If this is a hosted service; you may not have access to that setting and need to request permissions first or get your host to correct)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntumysql-5.7 package