package mysql-server 8.0.17-0ubuntu2 failed to install/upgrade: problèmes de dépendances - laissé non configuré

[jibe64]

After upgrading from Ubuntu 19.04 to 19.10, mysql doesn't works any more (error 2002 - database not found).
I tried uninstalling / installing, but no way, dkpg error on mysqld persists.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: mysql-server 8.0.17-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Fri Nov 8 09:27:42 2019
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2019-04-24 (197 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
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
MySQLVarLibDirListing: ['debian-5.7.flag', 'lencloitre', 'performance_schema', 'secure_login', 'auto.cnf', 'phpmyadmin', 'undo_002', 'binlog.index', 'adso', 'sys', 'undo_001', 'mysql', 'membres_adso', 'ib_logfile1', 'ibdata1', 'wordpress', 'mysql.ibd', 'mysql_upgrade_info', '#innodb_temp', 'lesjc86', 'seniors64', 'ib_buffer_pool', 'tpdb', 'ibtmp1', 'ib_logfile0']
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=014d5cf0-ee07-4bf5-ad4a-e3b96011ebc4 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt 1.9.4
SourcePackage: mysql-8.0
Title: package mysql-server 8.0.17-0ubuntu2 failed to install/upgrade: problèmes de dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)

[Rafael David Tinoco (rafaeldtinoco)]

This looks like a database corruption and not a MYSQL package bug:

2019-11-08T07:30:49.357992Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17-0ubuntu2) starting as process 1845
2019-11-08T07:30:50.096273Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 13
2019-11-08T07:30:50.096279Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 14
2019-11-08T07:30:50.096285Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 4294967293
2019-11-08T07:30:50.096292Z 1 [ERROR] [MY-012964] [InnoDB] Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)
2019-11-08T07:30:50.196716Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2019-11-08T07:30:50.596311Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2019-11-08T07:30:50.596411Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2019-11-08T07:30:50.597250Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-11-08T07:30:50.597565Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17-0ubuntu2) (Ubuntu).

You can try recovering your database by reading:

https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html

I'm marking this as incomplete. Feel free to mark it as "new" again if you still find this is a bug in mysql, hopefully showing us a way to reproduce the issue.

Thanks a lot!

Rafael

[jibe64 (jacques-s)]

Thank you for your reply.

I upgraded from Ubuntu 19.04 to 19.10 and things began to get wrong.
It looks like the update installed MariaDB instead of MYSQL8 and that it
was impossible then to remove mysql in order to reinstall it.
I wanted to remove mysql, because PHPmyadmin sent error 2002. And trying
downgrading failed, too.
I don't know if those elements may help.

I loaded a fresh image of Apache2 from Ubuntu website and found that,
now, it comes with MariaDB !

Regards,

Jacques

Le 11/11/2019 à 13:46, Rafael David Tinoco a écrit :
> This looks like a database corruption and not a MYSQL package bug:
>
> 2019-11-08T07:30:49.357992Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17-0ubuntu2) starting as process 1845
> 2019-11-08T07:30:50.096273Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 13
> 2019-11-08T07:30:50.096279Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 14
> 2019-11-08T07:30:50.096285Z 1 [ERROR] [MY-012179] [InnoDB] Could not find any file associated with the tablespace ID: 4294967293
> 2019-11-08T07:30:50.096292Z 1 [ERROR] [MY-012964] [InnoDB] Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)
> 2019-11-08T07:30:50.196716Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
> 2019-11-08T07:30:50.596311Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
> 2019-11-08T07:30:50.596411Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
> 2019-11-08T07:30:50.597250Z 0 [ERROR] [MY-010119] [Server] Aborting
> 2019-11-08T07:30:50.597565Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17-0ubuntu2) (Ubuntu).
>
> You can try recovering your database by reading:
>
> https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
>
> I'm marking this as incomplete. Feel free to mark it as "new" again if
> you still find this is a bug in mysql, hopefully showing us a way to
> reproduce the issue.
>
> Thanks a lot!
>
> Rafael
>
> ** Changed in: mysql-8.0 (Ubuntu)
> Status: New => Incomplete
>

[Andreas Hasenack (ahasenack)]

Ubuntu Eoan doesn't ship phpmyadmin, perhaps you got it from another place, and it had a dependency on mariadb instead of mysql? Perhaps you installed phpmyadmin from Debian, which uses mariadb instead of mysql?

[jibe64 (jacques-s)]

Thank you for your reply.
Carefully following instructions about installing mysql, I could
completely uninstall and reinstall mysql.
It works, now, but the version is actually 5.7.
I'll try to install ver 8.0 later.
Thanks for your support. You may close the topic.

Best regards.

Le 12/11/2019 à 22:17, Andreas Hasenack a écrit :
> Ubuntu Eoan doesn't ship phpmyadmin, perhaps you got it from another
> place, and it had a dependency on mariadb instead of mysql? Perhaps you
> installed phpmyadmin from Debian, which uses mariadb instead of mysql?
>

[Bryce Harrington (bryce)]

Thanks for getting back to us, I'll go ahead and close the bug report.