package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[juan cruz tron]

Ni Idea De Que Está Pasando Con Mi Paquete De MySQL; No Me Deja Ni Desinstalarlo Ni instalarlo, Mucho Menos Utilizarlo...

Ayudaa...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.17-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 mysql-server-5.7: Configure
 mysql-server: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Wed Apr 19 08:51:25 2017
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2017-03-05 (45 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215)
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: ['debian-5.7.flag', 'ib_logfile1', 'mythconverg', 'mysql_upgrade_info', 'ibdata1', 'debian-5.1.flag', 'ib_logfile0', 'mysql']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=61091c01-5a9d-4681-b1c1-dc95180ea318 ro persistent quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.17-0ubuntu0.16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Hi Juan,

From your logfiles:
2017-04-19T11:52:27.511052Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2017-04-19T11:52:27.511342Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-04-19T11:52:28.112231Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-19T11:52:28.112357Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-19T11:52:28.112399Z 0 [ERROR] Failed to initialize plugins.
2017-04-19T11:52:28.112431Z 0 [ERROR] Aborting

This is due to a configuration/setup error.
The default installation works and I can't derive from the logs what exactly changed your config and or DB to no more match.

I didn't see a bad config entry, but it might be in other included configs.
OTOH it could also be a broken DB file whatever the source for that might be.

It seems some year ago that happened a few times, I found [1] and a few similar posts.

You'd have to fix up config/DB file to match and work, then upgrades will work.
If it never worked and has no important data you might as well just purge (apt remove purge ...) it completely package/config/dbfile and start from scratch.

[1]: http://sharadchhetri.com/2014/11/29/upgrading-mysql-5-1-5-6-service-failed-start/

[Christian Ehrhardt  (paelzer)]

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.

[Launchpad Janitor (janitor)]

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]