sepackage mysql-server-5.7 5.7.28-0ubuntu0.18.04.4 failed to install/upgrade: instalado mysql-server-5.7 paquete post-installation guión el subproceso devolvió un error con estado de salida 1

[gustavo isaac chaile]

qqqqqqqqqq

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.28-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Mon Dec 16 13:19:19 2019
ErrorMessage: instalado mysql-server-5.7 paquete post-installation guión el subproceso devolvió un error con estado de salida 1
InstallationDate: Installed on 2016-02-11 (1403 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Logs.var.log.daemon.log:

Logs.var.log.mysql.error.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', 'ca.pem', 'ca-key.pem', 'ib_logfile1', 'ib_buffer_pool', 'debian-5.7.flag', 'client-key.pem', 'mysql', 'auto.cnf', 'private_key.pem', 'sys', 'ib_logfile0', 'server-key.pem', 'client-cert.pem', 'server-cert.pem', 'performance_schema', 'public_key.pem']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=35bf7ee4-cf2d-4ce1-89f5-030449c4765a ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt 1.6.12
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.28-0ubuntu0.18.04.4 failed to install/upgrade: instalado mysql-server-5.7 paquete post-installation guión el subproceso devolvió un error con estado de salida 1
UpgradeStatus: Upgraded to bionic on 2019-11-02 (44 days ago)

[Eduardo Barretto (ebarretto)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Rafael David Tinoco (rafaeldtinoco)]

Based on:

https://launchpadlibrarian.net/455937522/DpkgTerminalLog.txt

Looks like the instance (of mysql about to be upgraded) wasn't shutdown correctly:

dic 16 13:19:15 gustavo-net mysqld[16999]: 2019-12-16T16:19:15.241819Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
dic 16 13:19:15 gustavo-net systemd[1]: mysql.service: Failed with result 'exit-code'.
dic 16 13:19:15 gustavo-net systemd[1]: Failed to start MySQL Community Server.
dic 16 13:19:15 gustavo-net systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
dic 16 13:19:15 gustavo-net systemd[1]: mysql.service: Scheduled restart job, restart counter is at 3.
dic 16 13:19:15 gustavo-net systemd[1]: Stopped MySQL Community Server.
dic 16 13:19:15 gustavo-net systemd[1]: Starting MySQL Community Server...

And when the new instance (of upgraded mysql) tried to start:

dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596722Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596800Z 0 [Note] IPv6 is available.
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596818Z 0 [Note] - '::' resolves to '::';
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596862Z 0 [Note] Server socket created on IP: '::'.
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596897Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596910Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
dic 16 13:19:16 gustavo-net mysqld[17036]: 2019-12-16T16:19:16.596934Z 0 [ERROR] Aborting
dic 16 13:19:16 gustavo-net mysqld[17036]: Initialization of mysqld failed: 0

it couldn't bind() 3306 because it was already in use (or TIME_WAIT, perhaps, because of bad on-going connection closures).

Subscribing ubuntu-server to check if upgrade scripts can do anything regarding this, hopefully reducing the possibility of this happening during upgrades (or checking if it is worth).

[Andreas Hasenack (ahasenack)]

From the dpkg history log, it looks like you are mixing mariadb and mysql. I'm not sure transitioning from one to the other is supported, and in any case it's asking for trouble in my opinion. I suggest you pick one of the two.

For your current machine, I also suggest the following to try to fix it:

sudo apt update
sudo apt -f install

And then choose between mariadb and mysql.

[Launchpad Janitor (janitor)]

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