Could not open mysql.plugin table. Some plugins may be not loaded

Question

I have an issue with MySQL. When I'm trying to start it, that gives me an error message, which is

2015-12-10 10:52:31 13f4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-12-10 10:52:31 5108 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-12-10 10:52:31 5108 [Note] InnoDB: The InnoDB memory heap is disabled
2015-12-10 10:52:31 5108 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-12-10 10:52:31 5108 [Note] InnoDB: Memory barrier is not used
2015-12-10 10:52:31 5108 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-12-10 10:52:31 5108 [Note] InnoDB: Not using CPU crc32 instructions
2015-12-10 10:52:31 5108 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-12-10 10:52:31 5108 [Note] InnoDB: Completed initialization of buffer pool
2015-12-10 10:52:31 5108 [Note] InnoDB: Highest supported file format is Barracuda.
2015-12-10 10:52:31 5108 [Note] InnoDB: The log sequence numbers 1902092 and 1902092 in ibdata files do not match the log sequence number 1902102 in the ib_logfiles!
2015-12-10 10:52:31 5108 [Note] InnoDB: Database was not shutdown normally!
2015-12-10 10:52:31 5108 [Note] InnoDB: Starting crash recovery.
2015-12-10 10:52:31 5108 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-12-10 10:52:31 5108 [Note] InnoDB: Restoring possible half-written data pages 
2015-12-10 10:52:31 5108 [Note] InnoDB: from the doublewrite buffer...
2015-12-10 10:52:31 5108 [Note] InnoDB: 128 rollback segment(s) are active.
2015-12-10 10:52:31 5108 [Note] InnoDB: Waiting for purge to start
2015-12-10 10:52:32 5108 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1902102
2015-12-10 10:52:32 1760 [Note] InnoDB: Dumping buffer pool(s) not yet started
2015-12-10 10:52:32 5108 [Note] Plugin 'FEEDBACK' is disabled.
2015-12-10 10:52:32 5108 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2015-12-10 10:52:32 5108 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2015-12-10 10:52:32 5108 [Note] Server socket created on IP: '::'.
2015-12-10 10:52:32 5108 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist

I changed to InnoDB yesterday, but no problems were found. Any ideas?

Answer 1

So... in my particular case i had a quite old installation (10.3.31) of MariaDB on my Raspberry PI. One day, my system collapsed and I couldn't boot it up anymore so I had to make a copy of files from the SD card and move them to my new server instance. Even though my setup was very similar and I was getting the same exact error, I couldn't resolve it by applying the solutions proposed here.

What helped was:

1. Installing the exact same version of MariaDB from the manufacturer site.
2. Replacing all the contents of data dir with the old contents from the old machine.
3. running MariaDB in safe mode using mysqld_safe from the bin dir.

If your database files sit in another directory you might want to use the --datadir parameter like so:

# mysqld_safe --datadir=/var/lib/mysql/

Finally, from there I was able to dump the files to a .sql dump.

# mysqldump database -u root -p > dump.sql

Answer 2

I had the same error shown but I found a different solution. I found that my backup had a mysql database and my current data didn't have that. I placed back the mysql database and my database worked just fine again.

Answer 3

The suggestion by Mohit Verma works ...

For windows / xampp,

Stop mysql service Go to mysql/data directory Please take the backup of highlighted file in separate place and then delete it from data directory. ![][1]

Start Mysql service.

Answer 4

I have same problem too, I tried some solution that you told before but doesn't work. I tried replace one by one the tables/files in data/mysql with the new one (I got it from backup) and.. the problem solved when I replace db.* files.

So my MariaDb running again after I replace files db.frm, db.MAD, and db.MAI.

Answer 5

mv /var/lib/mysql/aria_log_control /var/lib/mysql/aria_log_control.orig 

this worked for me

from https://support.plesk.com/hc/en-us/articles/12377243101591-MariaDB-fails-to-start-Aria-engine-is-not-enabled-or-did-not-start

Answer 6

Simple solution:

There is a backup folder in the ..\Xampp\mysql directory. Copy its contents and paste in ..\Xampp\mysql\data. Then the error will be gone.

Answer 7

For windows / xampp,

1. Stop mysql service
2. Go to mysql/data directory
3. Please take the backup of highlighted file in separate place and then delete it from data directory.

4. Start Mysql service.

The above method solved the problem for me.

Answer 8

Just renamed these files and the issue fixed. After rename files next restart of mysql it will automatically create new files so no need to copy files from backup folder.

Answer 9

For my Windows XAMPP install, copying the files from the backup directory did clear the mysql error. However, it also reset my Wordpress install. I suspect that the underlying issue was a database corruption issue caused by the "bleeding edge" install of Wordpress on my local PC.

Answer 10

For Windows this worked for me Perfectly:

Close your xammp completely using Task Manager

removing these files in /xampp/mysql:

ib_logfile0
ib_logfile1
aria_log_control
aria_log.* ( * == some Number)

Start again your xampp.

Answer 11

For the xampp users, you just need to replace following files from Xampp/mysql/backup folder to Xampp/mysql/data folder (FYI: Keep a backup copy of data folder before actioning just to be on a safer side..)

Answer 12

From me it was /usr/bin/mariadbd process stock into the memory I was only manage to stop it with

sudo killall mariadbd

Answer 13

removing (renaming) this files in /var/lib/mysql:

ib_logfile0
ib_logfile1
aria_log_control

and restarting:

sudo service mysql start

solved it for me

Answer 14

I had this same FEEDBACK/plugins error using MariaDB 10.4 in Docker. Switching to MariaDB 10.3 solved it.

Answer 15

These instructions worked for me in a fresh install of MariaDB in Arch Linux:

systemctl stop mariadb
rm -R /var/lib/mysql/*
mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
systemctl start mariadb