MariaDB can't find tables mysql.user and mysql.serversWhy are simple SELECTs on InnoDB 100x slower than on...

Bitcoin automatically diverted to bech32 address

What have we got?

Taking an academic pseudonym?

Why does XLAT mean 'translate'?

Headless horseman claims new head

Why did Shae (falsely) implicate Sansa?

Discouraging missile alpha strikes

How to explain one side of Super Earth is smoother than the other side?

Is the "hot network questions" element on Stack Overflow a dark pattern?

How can a kingdom keep the secret of a missing monarchy from the public?

What prevents people from lying about where they live in order to reduce state income taxes?

Can you make a Spell Glyph of a spell that has the potential to target more than one creature?

I'm struggling to say 'struggle'

Ethernet cable only works in certain positions

What happens when the last remaining players refuse to kill each other?

How to assess the susceptibility of a U.S. company to go bankrupt?

How to make clear what a part-humanoid character looks like when they're quite common in their world?

How to draw these kind of adjacent ovals with arrows in latex?

Is 'bad luck' with former employees a red flag?

Does limiting the number of sources help simplify the game for a new DM with new and experienced players?

How can guns be countered by melee combat without raw-ability or exceptional explanations?

How to write pow math?

GPL - Is it required to post source code to the Public - when is a software released?

Sing Baby Shark



MariaDB can't find tables mysql.user and mysql.servers


Why are simple SELECTs on InnoDB 100x slower than on MyISAM?MariaDB/MySql Repository (Ubuntu 16.04) conflicts and moreChanging table types from MyISAM to InnoDB in a MySQLdump fileMariaDB service won't start (mysqld.sock not found)MariaDB memory usage growingSOLUTION - OOM Killer was killing mariadb every hour or soGSSAPI on MariaDBWhy is MDB 10.2.14 not handling deadlocks properly when it did prior to upgrade from 10.1.22Finding temporary table name in MariaDBMariaDB Spider Engine UDF spider_bg_direct_sql can't find TEMPORARY table













-2















I've been running MariaDB for some time now without problem. I did a minor version upgrade from 10.2.14 to 10.2.15 and now it refuses to start. If I'm reading the error logs correctly, it can't find the tables mysql.user and mysql.servers. I have confirmed that the data files exist, are not corrupted, and they appear to have the proper permissions.



MariaDB 10.2.15 running on Fedora 28.



This is the dump from the error log. 





2018-06-19 17:12:41 140244707127552 [Note] RocksDB: 2 column families found

2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Column Families at start:

2018-06-19 17:12:41 140244707127552 [Note]   cf=default

2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864

2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864

2018-06-19 17:12:41 140244707127552 [Note]   cf=__system__

2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864

2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864

2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Table_store: loaded DDL data for 0 tables

2018-06-19 17:12:41 140244707127552 [Note] RocksDB: global statistics using get_sched_indexer_t indexer

2018-06-19 17:12:41 140244707127552 [Note] MyRocks storage engine plugin has been successfully initialized.

Tue Jun 19 17:12:41 2018 PerconaFT recovery starting in env /var/lib/mysql/

Tue Jun 19 17:12:41 2018 PerconaFT recovery scanning backward from 1319

Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_end_checkpoint at 1319 timestamp 1529453469731997 xid 1315 (bw_newer)

Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_begin_checkpoint at 1315 timestamp 1529453469731991 (bw_between)

Tue Jun 19 17:12:41 2018 PerconaFT recovery turning around at begin checkpoint 1315 time 6

Tue Jun 19 17:12:41 2018 PerconaFT recovery starts scanning forward to 1319 from 1315 left 4 (fw_between)

Tue Jun 19 17:12:41 2018 PerconaFT recovery closing 2 dictionaries

Tue Jun 19 17:12:41 2018 PerconaFT recovery making a checkpoint

Tue Jun 19 17:12:41 2018 PerconaFT recovery done

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Uses event mutexes

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Compressed tables use zlib 1.2.11

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using Linux native AIO

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Number of pools: 1

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using SSE2 crc32 instructions

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Completed initialization of buffer pool

2018-06-19 17:12:41 140243754858240 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 128 out of 128 rollback segments are active.

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Creating shared tablespace for temporary tables

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Waiting for purge to start

2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 5.7.22 started; log sequence number 26491335405

2018-06-19 17:12:41 140243746465536 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2018-06-19 17:12:41 140244707127552 [Note] Plugin 'FEEDBACK' is disabled.

2018-06-19 17:12:41 140244707127552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded

2018-06-19 17:12:41 140244707127552 [Note] Recovering after a crash using tc.log

2018-06-19 17:12:41 140244707127552 [Note] Starting crash recovery...

2018-06-19 17:12:41 140244707127552 [Note] Crash recovery finished.

2018-06-19 17:12:41 140244707127552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist

2018-06-19 17:12:41 140244707127552 [Note] Server socket created on IP: '::'.

2018-06-19 17:12:41 140244707127552 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist


This the systemd output:





Starting MariaDB 10.2 database server...

mysql-prepare-db-dir[10435]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.

mysql-prepare-db-dir[10435]: If this is not the case, make sure the /var/lib/mysql is empty before running mysql-prepare-db-dir.

[Note] /usr/libexec/mysqld (mysqld 10.2.15-MariaDB) starting as process 10472 ...

systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

systemd[1]: mariadb.service: Failed with result 'exit-code'.

systemd[1]: Failed to start MariaDB 10.2 database server.


I've run myisamchk on all the tables in the data directory, and I've uninstalled and reinstalled the mariadb-server package. As far as I can tell it hasn't made a difference. Any thoughts?



UPDATE: this is the error message from running mysql_upgrade





mysql_upgrade --upgrade-system-tables

The --upgrade-system-tables option was used, user tables won't be touched.

This installation of MySQL is already upgraded to 10.2.15-MariaDB, use --force if you still need to run mysql_upgrade


So it shows them as having been upgraded. If I run with --force, I get this:





mysql_upgrade --upgrade-system-tables --force

The --upgrade-system-tables option was used, user tables won't be touched.

Phase 1/7: Checking and upgrading mysql database

Processing databases

mysql

mysql.column_stats                                 OK

mysql.columns_priv                                 OK

mysql.db                                           OK

mysql.event                                        OK

mysql.func                                         OK

mysql.help_category                                OK

mysql.help_keyword                                 OK

mysql.help_relation                                OK

mysql.help_topic                                   OK

mysql.host                                         OK

mysql.index_stats                                  OK

mysql.plugin                                       OK

mysql.proc                                         OK

mysql.procs_priv                                   OK

mysql.proxies_priv                                 OK

mysql.roles_mapping                                OK

mysql.servers                                      OK

mysql.table_stats                                  OK

mysql.tables_priv                                  OK

mysql.time_zone                                    OK

mysql.time_zone_leap_second                        OK

mysql.time_zone_name                               OK

mysql.time_zone_transition                         OK

mysql.time_zone_transition_type                    OK

mysql.user                                         OK

Phase 2/7: Installing used storage engines... Skipped

Phase 3/7: Fixing views... Skipped

Phase 4/7: Running 'mysql_fix_privilege_tables'

ERROR 1813 (HY000) at line 64: Tablespace for table '`mysql`.`innodb_table_stats`' exists. Please DISCARD the tablespace before IMPORT

ERROR 1813 (HY000) at line 68: Tablespace for table '`mysql`.`innodb_index_stats`' exists. Please DISCARD the tablespace before IMPORT

ERROR 1813 (HY000) at line 136: Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the tablespace before IMPORT

ERROR 1146 (42S02) at line 588: Table 'mysql.innodb_index_stats' doesn't exist

ERROR 1243 (HY000) at line 589: Unknown prepared statement handler (stmt) given to EXECUTE

ERROR 1146 (42S02) at line 591: Table 'mysql.innodb_table_stats' doesn't exist

ERROR 1243 (HY000) at line 592: Unknown prepared statement handler (stmt) given to EXECUTE

ERROR 1146 (42S02) at line 596: Table 'mysql.innodb_index_stats' doesn't exist

ERROR 1146 (42S02) at line 600: Table 'mysql.innodb_table_stats' doesn't exist

ERROR 1146 (42S02) at line 603: Table 'mysql.innodb_table_stats' doesn't exist

FATAL ERROR: Upgrade failed





mariadb myisam startup mariadb-10.2







share|improve this question





























    -2















    I've been running MariaDB for some time now without problem. I did a minor version upgrade from 10.2.14 to 10.2.15 and now it refuses to start. If I'm reading the error logs correctly, it can't find the tables mysql.user and mysql.servers. I have confirmed that the data files exist, are not corrupted, and they appear to have the proper permissions.



    MariaDB 10.2.15 running on Fedora 28.



    This is the dump from the error log. 




    
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: 2 column families found
    
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Column Families at start:
    
2018-06-19 17:12:41 140244707127552 [Note]   cf=default
    
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
    
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
    
2018-06-19 17:12:41 140244707127552 [Note]   cf=__system__
    
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
    
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
    
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Table_store: loaded DDL data for 0 tables
    
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: global statistics using get_sched_indexer_t indexer
    
2018-06-19 17:12:41 140244707127552 [Note] MyRocks storage engine plugin has been successfully initialized.
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery starting in env /var/lib/mysql/
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery scanning backward from 1319
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_end_checkpoint at 1319 timestamp 1529453469731997 xid 1315 (bw_newer)
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_begin_checkpoint at 1315 timestamp 1529453469731991 (bw_between)
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery turning around at begin checkpoint 1315 time 6
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery starts scanning forward to 1319 from 1315 left 4 (fw_between)
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery closing 2 dictionaries
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery making a checkpoint
    
Tue Jun 19 17:12:41 2018 PerconaFT recovery done
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Uses event mutexes
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Compressed tables use zlib 1.2.11
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using Linux native AIO
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Number of pools: 1
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using SSE2 crc32 instructions
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Completed initialization of buffer pool
    
2018-06-19 17:12:41 140243754858240 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Highest supported file format is Barracuda.
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 128 out of 128 rollback segments are active.
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Creating shared tablespace for temporary tables
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Waiting for purge to start
    
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 5.7.22 started; log sequence number 26491335405
    
2018-06-19 17:12:41 140243746465536 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    
2018-06-19 17:12:41 140244707127552 [Note] Plugin 'FEEDBACK' is disabled.
    
2018-06-19 17:12:41 140244707127552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
    
2018-06-19 17:12:41 140244707127552 [Note] Recovering after a crash using tc.log
    
2018-06-19 17:12:41 140244707127552 [Note] Starting crash recovery...
    
2018-06-19 17:12:41 140244707127552 [Note] Crash recovery finished.
    
2018-06-19 17:12:41 140244707127552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
    
2018-06-19 17:12:41 140244707127552 [Note] Server socket created on IP: '::'.
    
2018-06-19 17:12:41 140244707127552 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist


    This the systemd output:




    
Starting MariaDB 10.2 database server...
    
mysql-prepare-db-dir[10435]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
    
mysql-prepare-db-dir[10435]: If this is not the case, make sure the /var/lib/mysql is empty before running mysql-prepare-db-dir.
    
[Note] /usr/libexec/mysqld (mysqld 10.2.15-MariaDB) starting as process 10472 ...
    
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
    
systemd[1]: mariadb.service: Failed with result 'exit-code'.
    
systemd[1]: Failed to start MariaDB 10.2 database server.


    I've run myisamchk on all the tables in the data directory, and I've uninstalled and reinstalled the mariadb-server package. As far as I can tell it hasn't made a difference. Any thoughts?



    UPDATE: this is the error message from running mysql_upgrade




    
mysql_upgrade --upgrade-system-tables
    
The --upgrade-system-tables option was used, user tables won't be touched.
    
This installation of MySQL is already upgraded to 10.2.15-MariaDB, use --force if you still need to run mysql_upgrade


    So it shows them as having been upgraded. If I run with --force, I get this:




    
mysql_upgrade --upgrade-system-tables --force
    
The --upgrade-system-tables option was used, user tables won't be touched.
    
Phase 1/7: Checking and upgrading mysql database
    
Processing databases
    
mysql
    
mysql.column_stats                                 OK
    
mysql.columns_priv                                 OK
    
mysql.db                                           OK
    
mysql.event                                        OK
    
mysql.func                                         OK
    
mysql.help_category                                OK
    
mysql.help_keyword                                 OK
    
mysql.help_relation                                OK
    
mysql.help_topic                                   OK
    
mysql.host                                         OK
    
mysql.index_stats                                  OK
    
mysql.plugin                                       OK
    
mysql.proc                                         OK
    
mysql.procs_priv                                   OK
    
mysql.proxies_priv                                 OK
    
mysql.roles_mapping                                OK
    
mysql.servers                                      OK
    
mysql.table_stats                                  OK
    
mysql.tables_priv                                  OK
    
mysql.time_zone                                    OK
    
mysql.time_zone_leap_second                        OK
    
mysql.time_zone_name                               OK
    
mysql.time_zone_transition                         OK
    
mysql.time_zone_transition_type                    OK
    
mysql.user                                         OK
    
Phase 2/7: Installing used storage engines... Skipped
    
Phase 3/7: Fixing views... Skipped
    
Phase 4/7: Running 'mysql_fix_privilege_tables'
    
ERROR 1813 (HY000) at line 64: Tablespace for table '`mysql`.`innodb_table_stats`' exists. Please DISCARD the tablespace before IMPORT
    
ERROR 1813 (HY000) at line 68: Tablespace for table '`mysql`.`innodb_index_stats`' exists. Please DISCARD the tablespace before IMPORT
    
ERROR 1813 (HY000) at line 136: Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the tablespace before IMPORT
    
ERROR 1146 (42S02) at line 588: Table 'mysql.innodb_index_stats' doesn't exist
    
ERROR 1243 (HY000) at line 589: Unknown prepared statement handler (stmt) given to EXECUTE
    
ERROR 1146 (42S02) at line 591: Table 'mysql.innodb_table_stats' doesn't exist
    
ERROR 1243 (HY000) at line 592: Unknown prepared statement handler (stmt) given to EXECUTE
    
ERROR 1146 (42S02) at line 596: Table 'mysql.innodb_index_stats' doesn't exist
    
ERROR 1146 (42S02) at line 600: Table 'mysql.innodb_table_stats' doesn't exist
    
ERROR 1146 (42S02) at line 603: Table 'mysql.innodb_table_stats' doesn't exist
    
FATAL ERROR: Upgrade failed





    mariadb myisam startup mariadb-10.2







    share|improve this question



























      -2












      -2








      -2








      I've been running MariaDB for some time now without problem. I did a minor version upgrade from 10.2.14 to 10.2.15 and now it refuses to start. If I'm reading the error logs correctly, it can't find the tables mysql.user and mysql.servers. I have confirmed that the data files exist, are not corrupted, and they appear to have the proper permissions.



      MariaDB 10.2.15 running on Fedora 28.



      This is the dump from the error log. 




      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: 2 column families found
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Column Families at start:
      
2018-06-19 17:12:41 140244707127552 [Note]   cf=default
      
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]   cf=__system__
      
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Table_store: loaded DDL data for 0 tables
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: global statistics using get_sched_indexer_t indexer
      
2018-06-19 17:12:41 140244707127552 [Note] MyRocks storage engine plugin has been successfully initialized.
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery starting in env /var/lib/mysql/
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery scanning backward from 1319
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_end_checkpoint at 1319 timestamp 1529453469731997 xid 1315 (bw_newer)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_begin_checkpoint at 1315 timestamp 1529453469731991 (bw_between)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery turning around at begin checkpoint 1315 time 6
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery starts scanning forward to 1319 from 1315 left 4 (fw_between)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery closing 2 dictionaries
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery making a checkpoint
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery done
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Uses event mutexes
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Compressed tables use zlib 1.2.11
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using Linux native AIO
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Number of pools: 1
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using SSE2 crc32 instructions
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Completed initialization of buffer pool
      
2018-06-19 17:12:41 140243754858240 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Highest supported file format is Barracuda.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 128 out of 128 rollback segments are active.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Creating shared tablespace for temporary tables
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Waiting for purge to start
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 5.7.22 started; log sequence number 26491335405
      
2018-06-19 17:12:41 140243746465536 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      
2018-06-19 17:12:41 140244707127552 [Note] Plugin 'FEEDBACK' is disabled.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
      
2018-06-19 17:12:41 140244707127552 [Note] Recovering after a crash using tc.log
      
2018-06-19 17:12:41 140244707127552 [Note] Starting crash recovery...
      
2018-06-19 17:12:41 140244707127552 [Note] Crash recovery finished.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
      
2018-06-19 17:12:41 140244707127552 [Note] Server socket created on IP: '::'.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist


      This the systemd output:




      
Starting MariaDB 10.2 database server...
      
mysql-prepare-db-dir[10435]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
      
mysql-prepare-db-dir[10435]: If this is not the case, make sure the /var/lib/mysql is empty before running mysql-prepare-db-dir.
      
[Note] /usr/libexec/mysqld (mysqld 10.2.15-MariaDB) starting as process 10472 ...
      
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
      
systemd[1]: mariadb.service: Failed with result 'exit-code'.
      
systemd[1]: Failed to start MariaDB 10.2 database server.


      I've run myisamchk on all the tables in the data directory, and I've uninstalled and reinstalled the mariadb-server package. As far as I can tell it hasn't made a difference. Any thoughts?



      UPDATE: this is the error message from running mysql_upgrade




      
mysql_upgrade --upgrade-system-tables
      
The --upgrade-system-tables option was used, user tables won't be touched.
      
This installation of MySQL is already upgraded to 10.2.15-MariaDB, use --force if you still need to run mysql_upgrade


      So it shows them as having been upgraded. If I run with --force, I get this:




      
mysql_upgrade --upgrade-system-tables --force
      
The --upgrade-system-tables option was used, user tables won't be touched.
      
Phase 1/7: Checking and upgrading mysql database
      
Processing databases
      
mysql
      
mysql.column_stats                                 OK
      
mysql.columns_priv                                 OK
      
mysql.db                                           OK
      
mysql.event                                        OK
      
mysql.func                                         OK
      
mysql.help_category                                OK
      
mysql.help_keyword                                 OK
      
mysql.help_relation                                OK
      
mysql.help_topic                                   OK
      
mysql.host                                         OK
      
mysql.index_stats                                  OK
      
mysql.plugin                                       OK
      
mysql.proc                                         OK
      
mysql.procs_priv                                   OK
      
mysql.proxies_priv                                 OK
      
mysql.roles_mapping                                OK
      
mysql.servers                                      OK
      
mysql.table_stats                                  OK
      
mysql.tables_priv                                  OK
      
mysql.time_zone                                    OK
      
mysql.time_zone_leap_second                        OK
      
mysql.time_zone_name                               OK
      
mysql.time_zone_transition                         OK
      
mysql.time_zone_transition_type                    OK
      
mysql.user                                         OK
      
Phase 2/7: Installing used storage engines... Skipped
      
Phase 3/7: Fixing views... Skipped
      
Phase 4/7: Running 'mysql_fix_privilege_tables'
      
ERROR 1813 (HY000) at line 64: Tablespace for table '`mysql`.`innodb_table_stats`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1813 (HY000) at line 68: Tablespace for table '`mysql`.`innodb_index_stats`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1813 (HY000) at line 136: Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1146 (42S02) at line 588: Table 'mysql.innodb_index_stats' doesn't exist
      
ERROR 1243 (HY000) at line 589: Unknown prepared statement handler (stmt) given to EXECUTE
      
ERROR 1146 (42S02) at line 591: Table 'mysql.innodb_table_stats' doesn't exist
      
ERROR 1243 (HY000) at line 592: Unknown prepared statement handler (stmt) given to EXECUTE
      
ERROR 1146 (42S02) at line 596: Table 'mysql.innodb_index_stats' doesn't exist
      
ERROR 1146 (42S02) at line 600: Table 'mysql.innodb_table_stats' doesn't exist
      
ERROR 1146 (42S02) at line 603: Table 'mysql.innodb_table_stats' doesn't exist
      
FATAL ERROR: Upgrade failed





      mariadb myisam startup mariadb-10.2







      share|improve this question
















      I've been running MariaDB for some time now without problem. I did a minor version upgrade from 10.2.14 to 10.2.15 and now it refuses to start. If I'm reading the error logs correctly, it can't find the tables mysql.user and mysql.servers. I have confirmed that the data files exist, are not corrupted, and they appear to have the proper permissions.



      MariaDB 10.2.15 running on Fedora 28.



      This is the dump from the error log. 




      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: 2 column families found
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Column Families at start:
      
2018-06-19 17:12:41 140244707127552 [Note]   cf=default
      
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]   cf=__system__
      
2018-06-19 17:12:41 140244707127552 [Note]     write_buffer_size=67108864
      
2018-06-19 17:12:41 140244707127552 [Note]     target_file_size_base=67108864
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: Table_store: loaded DDL data for 0 tables
      
2018-06-19 17:12:41 140244707127552 [Note] RocksDB: global statistics using get_sched_indexer_t indexer
      
2018-06-19 17:12:41 140244707127552 [Note] MyRocks storage engine plugin has been successfully initialized.
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery starting in env /var/lib/mysql/
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery scanning backward from 1319
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_end_checkpoint at 1319 timestamp 1529453469731997 xid 1315 (bw_newer)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery bw_begin_checkpoint at 1315 timestamp 1529453469731991 (bw_between)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery turning around at begin checkpoint 1315 time 6
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery starts scanning forward to 1319 from 1315 left 4 (fw_between)
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery closing 2 dictionaries
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery making a checkpoint
      
Tue Jun 19 17:12:41 2018 PerconaFT recovery done
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Uses event mutexes
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Compressed tables use zlib 1.2.11
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using Linux native AIO
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Number of pools: 1
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Using SSE2 crc32 instructions
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Completed initialization of buffer pool
      
2018-06-19 17:12:41 140243754858240 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Highest supported file format is Barracuda.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 128 out of 128 rollback segments are active.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Creating shared tablespace for temporary tables
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: Waiting for purge to start
      
2018-06-19 17:12:41 140244707127552 [Note] InnoDB: 5.7.22 started; log sequence number 26491335405
      
2018-06-19 17:12:41 140243746465536 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      
2018-06-19 17:12:41 140244707127552 [Note] Plugin 'FEEDBACK' is disabled.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
      
2018-06-19 17:12:41 140244707127552 [Note] Recovering after a crash using tc.log
      
2018-06-19 17:12:41 140244707127552 [Note] Starting crash recovery...
      
2018-06-19 17:12:41 140244707127552 [Note] Crash recovery finished.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
      
2018-06-19 17:12:41 140244707127552 [Note] Server socket created on IP: '::'.
      
2018-06-19 17:12:41 140244707127552 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist


      This the systemd output:




      
Starting MariaDB 10.2 database server...
      
mysql-prepare-db-dir[10435]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
      
mysql-prepare-db-dir[10435]: If this is not the case, make sure the /var/lib/mysql is empty before running mysql-prepare-db-dir.
      
[Note] /usr/libexec/mysqld (mysqld 10.2.15-MariaDB) starting as process 10472 ...
      
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
      
systemd[1]: mariadb.service: Failed with result 'exit-code'.
      
systemd[1]: Failed to start MariaDB 10.2 database server.


      I've run myisamchk on all the tables in the data directory, and I've uninstalled and reinstalled the mariadb-server package. As far as I can tell it hasn't made a difference. Any thoughts?



      UPDATE: this is the error message from running mysql_upgrade




      
mysql_upgrade --upgrade-system-tables
      
The --upgrade-system-tables option was used, user tables won't be touched.
      
This installation of MySQL is already upgraded to 10.2.15-MariaDB, use --force if you still need to run mysql_upgrade


      So it shows them as having been upgraded. If I run with --force, I get this:




      
mysql_upgrade --upgrade-system-tables --force
      
The --upgrade-system-tables option was used, user tables won't be touched.
      
Phase 1/7: Checking and upgrading mysql database
      
Processing databases
      
mysql
      
mysql.column_stats                                 OK
      
mysql.columns_priv                                 OK
      
mysql.db                                           OK
      
mysql.event                                        OK
      
mysql.func                                         OK
      
mysql.help_category                                OK
      
mysql.help_keyword                                 OK
      
mysql.help_relation                                OK
      
mysql.help_topic                                   OK
      
mysql.host                                         OK
      
mysql.index_stats                                  OK
      
mysql.plugin                                       OK
      
mysql.proc                                         OK
      
mysql.procs_priv                                   OK
      
mysql.proxies_priv                                 OK
      
mysql.roles_mapping                                OK
      
mysql.servers                                      OK
      
mysql.table_stats                                  OK
      
mysql.tables_priv                                  OK
      
mysql.time_zone                                    OK
      
mysql.time_zone_leap_second                        OK
      
mysql.time_zone_name                               OK
      
mysql.time_zone_transition                         OK
      
mysql.time_zone_transition_type                    OK
      
mysql.user                                         OK
      
Phase 2/7: Installing used storage engines... Skipped
      
Phase 3/7: Fixing views... Skipped
      
Phase 4/7: Running 'mysql_fix_privilege_tables'
      
ERROR 1813 (HY000) at line 64: Tablespace for table '`mysql`.`innodb_table_stats`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1813 (HY000) at line 68: Tablespace for table '`mysql`.`innodb_index_stats`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1813 (HY000) at line 136: Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the tablespace before IMPORT
      
ERROR 1146 (42S02) at line 588: Table 'mysql.innodb_index_stats' doesn't exist
      
ERROR 1243 (HY000) at line 589: Unknown prepared statement handler (stmt) given to EXECUTE
      
ERROR 1146 (42S02) at line 591: Table 'mysql.innodb_table_stats' doesn't exist
      
ERROR 1243 (HY000) at line 592: Unknown prepared statement handler (stmt) given to EXECUTE
      
ERROR 1146 (42S02) at line 596: Table 'mysql.innodb_index_stats' doesn't exist
      
ERROR 1146 (42S02) at line 600: Table 'mysql.innodb_table_stats' doesn't exist
      
ERROR 1146 (42S02) at line 603: Table 'mysql.innodb_table_stats' doesn't exist
      
FATAL ERROR: Upgrade failed





      mariadb myisam startup mariadb-10.2




      mariadb myisam startup mariadb-10.2






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 21 '18 at 14:01







      Glen Davis

















      asked Jun 20 '18 at 0:38









      Glen DavisGlen Davis

      11




      11






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Answer left by the question author in a comment



          The frm files for the affected tables were missing (such as innodb_table_stats.frm) . I was able to retrieve copies from a backup directory. I stopped the server, copied the files over, and started the server again.



          I was also able to copy over files for the tables user and servers. I did have to run restorecon on them to make them play nice with SELinux. After that I wound up having to reauthorize all the database permissions for each user other than root.



          As far as I can tell, everything is working fine now.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f210078%2fmariadb-cant-find-tables-mysql-user-and-mysql-servers%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Answer left by the question author in a comment



            The frm files for the affected tables were missing (such as innodb_table_stats.frm) . I was able to retrieve copies from a backup directory. I stopped the server, copied the files over, and started the server again.



            I was also able to copy over files for the tables user and servers. I did have to run restorecon on them to make them play nice with SELinux. After that I wound up having to reauthorize all the database permissions for each user other than root.



            As far as I can tell, everything is working fine now.






            share|improve this answer




























              0














              Answer left by the question author in a comment



              The frm files for the affected tables were missing (such as innodb_table_stats.frm) . I was able to retrieve copies from a backup directory. I stopped the server, copied the files over, and started the server again.



              I was also able to copy over files for the tables user and servers. I did have to run restorecon on them to make them play nice with SELinux. After that I wound up having to reauthorize all the database permissions for each user other than root.



              As far as I can tell, everything is working fine now.






              share|improve this answer


























                0












                0








                0







                Answer left by the question author in a comment



                The frm files for the affected tables were missing (such as innodb_table_stats.frm) . I was able to retrieve copies from a backup directory. I stopped the server, copied the files over, and started the server again.



                I was also able to copy over files for the tables user and servers. I did have to run restorecon on them to make them play nice with SELinux. After that I wound up having to reauthorize all the database permissions for each user other than root.



                As far as I can tell, everything is working fine now.






                share|improve this answer













                Answer left by the question author in a comment



                The frm files for the affected tables were missing (such as innodb_table_stats.frm) . I was able to retrieve copies from a backup directory. I stopped the server, copied the files over, and started the server again.



                I was also able to copy over files for the tables user and servers. I did have to run restorecon on them to make them play nice with SELinux. After that I wound up having to reauthorize all the database permissions for each user other than root.



                As far as I can tell, everything is working fine now.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 15 mins ago









                Comment ConverterComment Converter

                1,2471325




                1,2471325






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid …



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f210078%2fmariadb-cant-find-tables-mysql-user-and-mysql-servers%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    -

                    Popular posts from this blog

                    ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

                    Image
                    Do I need to convey a moral for each of my blog post? Does convergence of polynomials imply that of its coefficients? Are hand made posters acceptable in Academia? How to read string as hex number in bash? Have the tides ever turned twice on any open problem? How do researchers send unsolicited emails asking for feedback on their works? How to determine the greatest d orbital splitting? When did hardware antialiasing start being available? How to test the sharpness of a knife? Asserting that Atheism and Theism are both faith based positions Print a physical multiplication table
                    Read more

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    Image
                    Should corporate security training be tailored based on a users' job role? Does human life have innate value over that of other animals? Limit involving inverse functions Father gets chickenpox, but doesn't infect his two children. How is this possible? Is it possible to re-order a List of continous entries? Who, if anyone, was the first astronaut to return to earth in a different vessel? The totem pole can be grouped into Identical projects by students at two different colleges: still plagiarism? Sci fi book, man buys a beat up spaceship and intervenes in a civil war on a planet and eventually becomes a space cop How to not
                    Read more

                    Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...

                    Image
                    Circunscripciones electorales del Senado de EspañaCircunscripciones electorales del Congreso de los DiputadosCircunscripciones electorales del Parlamento Vasco españolasCongreso de los DiputadosSenadobajaaltaPaís Vascoelecciones autonómicasprovincia homónima Localización de la circunscripción electoral de Guipúzcoa. Guipúzcoa es una de las 52 circunscripciones electorales españolas utilizadas como distritos electorales para el Congreso de los Diputados y el Senado, que son las cámaras baja y alta del Parlamento Español. [ 1 ] ​ Le corresponden 6 diputados y 4 senadores. También es una de las 3 circunscripciones electorales del País Vasco para las elecciones autonómicas, en que elige 25 parlamentarios. Se corresponde con la provincia homónima. [ 2 ] ​ Referencias ↑ Las claves del sistema electoral en España ↑ Resultados de las elecciones autonómicas de 2012 en Guipúzcoa This page is only for reference, If you need detailed information, please check here
                    Read more