package mysql-server-5.7 5.7.17-0ubuntu0.16.04.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 126
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Настраивается пакет mysql-server-5.7 (5.7.17-
Renaming removed key_buffer and myisam-recover options (if present)
ERROR: Unable to start MySQL server:
/var/lib/
Please take a look at https:/
Once the problem is resolved, run apt-get --fix-broken install to retry.
dpkg: ошибка при обработке пакета mysql-server-5.7 (--configure):
подпроцесс установлен сценарий post-installation возвратил код ошибки 126
dpkg: зависимости пакетов не позволяют настроить пакет mysql-server:
mysql-server зависит от mysql-server-5.7, однако:
Пакет mysql-server-5.7 пока не настроен.
dpkg: ошибка при обработке пакета mysql-server (--configure):
проблемы зависимостей — оставляем не настроенным
Отчёты apport не записаны, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа.
mysql-server-5.7
mysql-server
N: Файл «50unattended-
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.17-
ProcVersionSign
Uname: Linux 4.4.0-65-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Sun Apr 23 22:54:59 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 126
InstallationDate: Installed on 2012-10-10 (1656 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Logs.var.
Logs.var.
MySQLConf.
MySQLConf.
[mysqld_safe]
syslog
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.17-
UpgradeStatus: Upgraded to xenial on 2017-02-28 (54 days ago)
Hi,
that error seems odd, it is usually when a executable can not be executed due to e.g. wrong architecture.
Could you run and report back the following things: architecture architectures bin/mysqld
$ dpkg --print-
$ dpkg --print-
$ uname -a
$ file /usr/local/
Also the path indicated that this is not a normal Ubuntu mysql - that would have been in /usr/sbin/mysqld
So please report:
$ dpkg -S /usr/sbin/mysqld
If no package is owning this then you have some sort of third party mysql that is not supported.
If unintentionally there remove it, generally ../local/... takes precedence over other paths so the startup might pick this broken one up unintentionally.