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

Bug #1788544 reported by Karmeshwer Singh
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Distribution information:
Description: Ubuntu 18.04.1 LTS
Release: 18.04

k@k-HP-EliteBook-8460p:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

package installer information:chmod 755 bitnami-lampstack-7.0.31-1-linux-x64-installer.run

Below is the information of terminal:
It is in attachment kindly see to it

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.23-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 23 10:42:44 2018
DuplicateSignature:
 package:mysql-server-5.7:5.7.23-0ubuntu0.18.04.1
 Setting up mysql-server-5.7 (5.7.23-0ubuntu0.18.04.1) ...
 update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
 dpkg: error processing package mysql-server-5.7 (--configure):
  installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-08-22 (0 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: ['ib_buffer_pool', 'ibdata1', 'sys', 'ib_logfile1', 'performance_schema', 'auto.cnf', 'ib_logfile0', 'debian-5.7.flag', 'mysql']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=95dc814b-1e0b-408d-9bb0-a1972f61eeda ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3ubuntu0.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.23-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)

Revision history for this message
Karmeshwer Singh (k.s00) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
you seem to have all kinds of services already running, in your log I found:

Apache stumbling:
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Aug 23 10:42:05 k-HP-EliteBook-8460p apachectl[7951]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

And also mysql later:
2018-08-23T05:12:42.584400Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2018-08-23T05:12:42.584406Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2018-08-23T05:12:42.584423Z 0 [ERROR] Aborting

I can't derive from the logs what you had on these ports, but you'll need to resolve that cleanly (uninstall or reconfigure the former processes to other ports) or the new services won't start.
In general multiple webservers on different ports usually work, but multiple mysql databases I want to encourage you to double check their data path to not kill your DB content at some point.

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-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.