ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)

Bug #1828324 reported by mohamed samir hassan aly
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

sa

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: mysql-server-5.7 (not installed)
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Wed May 8 22:56:10 2019
ErrorMessage: new mysql-server-5.7 package pre-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2019-05-08 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt 1.7.4
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 (not installed) failed to install/upgrade: new mysql-server-5.7 package pre-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2019-04-12T06:45:43
mtime.conffile..etc.init.d.mysql: 2019-02-06T00:53:10
mtime.conffile..etc.logrotate.d.mysql-server: 2019-02-06T00:53:10
mtime.conffile..etc.mysql.debian-start: 2019-02-06T00:53:10

Revision history for this message
mohamed samir hassan aly (engmohamed) wrote :
Revision history for this message
Alex Murray (alexmurray) wrote : Bug is not a security issue

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.

information type: Private Security → Public
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

You have removed mysql at
 2019-05-08 22:38:38
And then (re)installed it at
  2019-05-08 22:55:45

But the log shows:
  invoke-rc.d returned 5
  There is a MySQL server running, but we failed in our attempts to stop it.
  Stop it yourself and try again!

So clearly there is something else running it can't get rid of.
That is custom to your system config and not reproducible in a simple test that I've done.

You'd need to check what is still running that it fails on and resolve that situation.

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.

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.