package mysql-server 5.7.18-0ubuntu0.16.10.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

Bug #1700675 reported by luis sosa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

a veces no funciona el servidor

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: mysql-server 5.7.18-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
AptOrdering:
 apache2:amd64: Install
 apache2-bin:amd64: Install
 apache2-utils:amd64: Install
 apache2-data:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Jun 26 16:50:55 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-02-17 (130 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
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: ['ib_logfile1', 'ib_buffer_pool', 'db_ws', 'phpmyadmin', 'db_site', 'db_sass', 'mysql', 'swpa', 'ibtmp1', 'db_gojunker', 'fact', 'sys', 'DB_DVMS', 'db_wshop', 'ibdata12', 'empleados', 'tienda24', 'performance_schema', 'debian-5.7.flag', 'ibdata1', 'ib_logfile0', 'auto.cnf']
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=baaf064c-9d1b-4444-ab3a-355528ebe4b6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt 1.3.5
SourcePackage: mysql-5.7
Title: package mysql-server 5.7.18-0ubuntu0.16.10.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.mysql.mysql.cnf: [modified]
mtime.conffile..etc.mysql.mysql.cnf: 2017-06-13T01:04:01.040085

Revision history for this message
luis sosa (lsosa81) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :

From mysql error log:

2017-06-26T22:50:59.900421Z 0 [ERROR] [FATAL] InnoDB: Tablespace id is 54 in the data dictionary but in file ./mysql/plugin.ibd it is 2!
2017-06-26 16:50:59 0x7f0e9e9dd6c0 InnoDB: Assertion failure in thread 139700767413952 in file ut0ut.cc line 916
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
22:50:59 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

further down:

2017-06-27T00:42:28.280897Z 0 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`servers` in the cache. Attempting to load the tablespace with space id 55
2017-06-27T00:42:28.281127Z 0 [ERROR] InnoDB: In file './mysql/servers.ibd', tablespace id and flags are 3 and 33, but in the InnoDB data dictionary they are 55 and 33. Have you moved InnoDB .ibd files around without using the commands DISCARD TABLESPACE and IMPORT TABLESPACE? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2017-06-27T00:42:28.281138Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2017-06-27T00:42:28.281146Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2017-06-27T00:42:28.281153Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `mysql/servers`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2017-06-27T00:42:28.281214Z 0 [Warning] InnoDB: Cannot calculate statistics for table `mysql`.`servers` because the .ibd file is missing. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2017-06-27T00:42:28.281260Z 0 [ERROR] Can't open and lock privilege tables: Tablespace is missing for table `mysql`.`servers`.

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to file a bug report.

I would recommend backing up your data and reinstalling the database
due to those errors about something being very wrong. It would be
interesting to know how you go in this state in the first place.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
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".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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.