package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 1

Bug #1898062 reported by AGA
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Trying to upgrade form 18.04 to 20.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.21-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Oct 1 16:47:31 2020
ErrorMessage: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 1
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: ['ibdata1', 'acadesa', 'radius', 'private_key.pem', 'ib_buffer_pool', 'performance_schema', 'client-key.pem', 'auto.cnf', 'ib_logfile1', 'master.info', 'mysql', 'server-cert.pem', 'server-key.pem', 'mysql_upgrade_info', 'sys', 'phpmyadmin', 'relay-log.info', 'public_key.pem', 'acages', 'debian-5.7.flag', 'client-cert.pem', 'ca.pem', 'ca-key.pem', 'ib_logfile0', 'acatestdesa']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=4e5cc7d2-6a34-11e8-a879-78e7d1f7008a ro maybe-ubiquity
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: el subproceso instalado paquete mysql-server-8.0 script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to focal on 2020-10-01 (0 days ago)
modified.conffile..etc.mysql.mysql.cnf: [modified]
modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified]
mtime.conffile..etc.mysql.mysql.cnf: 2018-06-22T16:12:38.770722
mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: 2020-10-01T16:47:31.096346

Revision history for this message
AGA (pn679964920) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
you kept your old config (fine) but now the new version complains on certain settings.
From your log

ERROR: Unable to start MySQL server:
2020-10-01T14:47:31.141085Z 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.
2020-10-01T14:47:31.141100Z 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.
2020-10-01T14:47:31.141116Z 0 [ERROR] [MY-000077] [Server] /usr/sbin/mysqld: Error while setting value 'STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' to 'sql_mode'.
2020-10-01T14:47:31.143961Z 0 [ERROR] [MY-010119] [Server] Aborting

You need to adapt those for the server to work after the upgrade.

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.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

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

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

Changed in mysql-8.0 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.