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

[Farhan Tanvir Utshaw]

After restarting my Ubuntu-18.04 LTS powered Dell-inspiron-3443 I got this error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.24-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Jan 2 13:14:02 2019
ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-08-06 (150 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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: ['rupantordb', 'auto.cnf', 'ib_logfile0', 'mysql', 'ibdata1', 'ib_buffer_pool', 'mysql_upgrade_info', 'debian-5.7.flag', 'ibtmp1', 'ib_logfile1', 'sys', 'performance_schema', 'hb_student_tracker']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=158b6b86-ddba-4547-adcb-ed9e0dd60bf1 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.6
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

Hi,
from your log at the time this happened

2019-01-02T07:14:00.977793Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190102 13:14:00
2019-01-02T07:14:00.980414Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2019-01-02T07:14:00.980436Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2019-01-02T07:14:00.980443Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2019-01-02T07:14:00.980465Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2019-01-02T07:14:00.980477Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2019-01-02T07:14:00.980480Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2019-01-02T07:14:00.980492Z 0 [ERROR] Aborting

That matches the localized "Wed Jan 2 13:14:02 2019" time

It seems that at that time some other service was running on that port and that broke the restart which is part of the upgrade procedure of a service.

[Christian Ehrhardt  (paelzer)]

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.

[Launchpad Janitor (janitor)]

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