package mysql-server-5.7 5.7.23-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess installed mysql-server-5.7 package post-installation script gab den Fehler-Ausgangsstatus 127 zurück
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
installation aborted.
Ubuntu 18.04.1 LTS
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.23-
ProcVersionSign
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
mysql-
libevent-
mysql-
mysql-
NULL: ConfigurePending
Architecture: amd64
Date: Sun Aug 26 10:50:58 2018
ErrorMessage: Unterprozess installed mysql-server-5.7 package post-installation script gab den Fehler-
InstallationDate: Installed on 2018-08-18 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Logs.var.
MySQLConf.
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.3ubuntu0.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.23-
UpgradeStatus: No upgrade log present (probably fresh install)
Thanks for filing this bug in Ubuntu.
I don't know what you did, but somehow you ended up missing an important file: dpkg/info/ mysql-server- 5.7.postinst: Zeile 191: /usr/share/ mysql-common/ configure- symlinks: Datei oder Verzeichnis nicht gefunden Ausgangsstatus 127 zurück
/var/lib/
[1mdpkg:[0m Fehler beim Bearbeiten des Paketes mysql-server-5.7 (--configure):
Unterprozess installed mysql-server-5.7 package post-installation script gab den Fehler-
That file (configure- symlinks) is part of the mysql-common package.
I suggest you try to install, or reinstall, it. Something like:
sudo apt update
sudo apt install mysql-common
or
sudo apt install --reinstall mysql-common
and finally
sudo apt -f install
Other than that, there isn't much else that can be suggested because there is no clear indication of a bug here, with steps to reproduce it, just a support request.