Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Hello to everyone!
I had recently made a fresh install of Debian 9.6 which uses MariaDB 10.1. Previously I was using 8.5 with MySQL 8.1 (which I still have on another partition).
I found several issues with the usage of my databases. But there is one specific error which is annoying:
ene 17 08:06:38 <machine> mysqld[1546]: 2019-01-17 8:06:38 140578977008384 [Warning] InnoDB: Cannot open table <db>/<table> from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
I get this error for every table on the DB. There are no other errors related to MySQL or MariaDB engine.
I have read the reference URL. Permissions are fine for /var/lib/mysql. No disk quota enabled. Plenty of space left on disk.Reading the correct my.cnf file.
I read the post below just a few days before your OP here.
I thought there was a reference to maria in the article -
Reading again I can't find maria, so here it is with reference to mysql transactions
from the developer of Gnocchi https://julien.danjou.info/why-you-shou ... sactional/
The operator have to determine where the upgrade script stopped, roll back the upgrade by itself, fix the failure, and rerun the upgrade procedure.
The developer must anticipate every case of potential upgrade failure, write a roll back procedure for each of this case by and test every one of those cases.
Use a database system that handles transactional DDL.
https://julien.danjou.info/gnocchi-4-3-0-released/
It probably wouldn't give an answer to your immediate needs with mariaDB
although may still give some clues to the types of errors like the one you show.
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
I do not see any relation with my issue. And the fact that you may have read maria does not either make it related as that article talks about transactions.
llivv wrote:I read the post below just a few days before your OP here.
I thought there was a reference to maria in the article -
Reading again I can't find maria, so here it is with reference to mysql transactions
from the developer of Gnocchi https://julien.danjou.info/why-you-shou ... sactional/
The operator have to determine where the upgrade script stopped, roll back the upgrade by itself, fix the failure, and rerun the upgrade procedure.
The developer must anticipate every case of potential upgrade failure, write a roll back procedure for each of this case by and test every one of those cases.
Use a database system that handles transactional DDL.
https://julien.danjou.info/gnocchi-4-3-0-released/
It probably wouldn't give an answer to your immediate needs with mariaDB
although may still give some clues to the types of errors like the one you show.