package mysql-server-5.7 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Running 17.10 (Artful) upgraded from 17.04 (Zesty). I was trying to correct an issue where I was unable to run mysql and was receiving the following error:
`ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)`
Tried uninstalling and reinstalling, didn't clear the error and now I'm getting errors about broken packages. Need this fixed, and need to be able to run mysql. For some reason, MariaDB was a dependency, but now that just seems to have messed everything up.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: mysql-server-5.7 (not installed)
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Fri Nov 3 11:11:29 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationDate: Installed on 2017-07-26 (100 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageV
dpkg 1.18.24ubuntu1
apt 1.5
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to artful on 2017-10-20 (14 days ago)
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
mtime.conffile.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since there isn't enough information in your report to differentiate between a local configuration problem and 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.