[Maria-discuss] After Fedora 22->23 update maria db doesn't start
From the log after systemctl restart mariadb.service:
InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 583845802 151124 9:51:40 [Note] Plugin 'FEEDBACK' is disabled. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/plugin 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. 151124 9:51:40 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/servers 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. 151124 9:51:40 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist in engine 151124 9:51:40 [Note] Server socket created on IP: '::'. 151124 9:51:40 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 151124 09:51:40 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended Trying other things [root@tiger ~]# mysqld_safe -uroot 151124 10:24:03 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. 151124 10:24:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 151124 10:24:03 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended [root@tiger ~]# mysql_upgrade Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory") FATAL ERROR: Upgrade failed [root@tiger ~]#
Am 24.11.2015 um 11:25 schrieb Carl Whalley:
From the log after systemctl restart mariadb.service:
InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 583845802 151124 9:51:40 [Note] Plugin 'FEEDBACK' is disabled. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/plugin 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. 151124 9:51:40 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/servers 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. 151124 9:51:40 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist in engine 151124 9:51:40 [Note] Server socket created on IP: '::'. 151124 9:51:40 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 151124 09:51:40 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
i wonder what is going wrong here because Fedora 22/23 have the same MariaDB version when i look at https://koji.fedoraproject.org/koji/packageinfo?packageID=15262 since i use my self-compiled packages with unchanged SPEC files from Fedora 21 to Fedora 23 without any issues i suggest ask the Fedora package maintainers anyways, mysql_upgrade can't work when the server don't start at all
Thanks . I tried also the obvious, complete removal and reinstallation with the same results :-( [root@tiger log]# dnf remove mariadb mariadb-server Dependencies resolved. ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Removing: mariadb x86_64 1:10.0.21-1.fc23 @updates 37 M mariadb-server x86_64 1:10.0.21-1.fc23 @updates 86 M Transaction Summary ============================================================================================================================================================================================================================================= Remove 2 Packages Installed size: 124 M Is this ok [y/N]: y Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Erasing : mariadb-server-1:10.0.21-1.fc23.x86_64 1/2 Erasing : mariadb-1:10.0.21-1.fc23.x86_64 2/2 Verifying : mariadb-server-1:10.0.21-1.fc23.x86_64 1/2 Verifying : mariadb-1:10.0.21-1.fc23.x86_64 2/2 Removed: mariadb.x86_64 1:10.0.21-1.fc23 mariadb-server.x86_64 1:10.0.21-1.fc23 Complete! [root@tiger log]# dnf install mariadb mariadb-server Failed to synchronize cache for repo 'Dropbox' from ' http://linux.dropbox.com/fedora/23/': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried, disabling. Last metadata expiration check performed 1:07:58 ago on Tue Nov 24 10:51:11 2015. Dependencies resolved. ============================================================================================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================================================================================= Installing: mariadb x86_64 1:10.0.21-1.fc23 updates 6.0 M mariadb-server x86_64 1:10.0.21-1.fc23 updates 18 M Transaction Summary ============================================================================================================================================================================================================================================= Install 2 Packages Total download size: 24 M Installed size: 124 M Is this ok [y/N]: y Downloading Packages: (1/2): mariadb-10.0.21-1.fc23.x86_64.rpm 1.8 MB/s | 6.0 MB 00:03 (2/2): mariadb-server-10.0.21-1.fc23.x86_64.rpm 1.1 MB/s | 18 MB 00:16 --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 1.3 MB/s | 24 MB 00:18 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : mariadb-1:10.0.21-1.fc23.x86_64 1/2 Installing : mariadb-server-1:10.0.21-1.fc23.x86_64 2/2 Verifying : mariadb-1:10.0.21-1.fc23.x86_64 1/2 Verifying : mariadb-server-1:10.0.21-1.fc23.x86_64 2/2 Installed: mariadb.x86_64 1:10.0.21-1.fc23 mariadb-server.x86_64 1:10.0.21-1.fc23 Complete! [root@tiger log]# systemctl restart mariadb.service Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. [root@tiger log]# On Tue, Nov 24, 2015 at 11:40 AM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 11:25 schrieb Carl Whalley:
From the log after systemctl restart mariadb.service:
InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 583845802 151124 9:51:40 [Note] Plugin 'FEEDBACK' is disabled. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/plugin 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. 151124 9:51:40 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: wrong number of columns in SYS_INDEXES record 151124 9:51:40 [Warning] InnoDB: Cannot open table mysql/servers 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. 151124 9:51:40 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist in engine 151124 9:51:40 [Note] Server socket created on IP: '::'. 151124 9:51:40 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format. 151124 09:51:40 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
i wonder what is going wrong here because Fedora 22/23 have the same MariaDB version when i look at https://koji.fedoraproject.org/koji/packageinfo?packageID=15262
since i use my self-compiled packages with unchanged SPEC files from Fedora 21 to Fedora 23 without any issues i suggest ask the Fedora package maintainers
anyways, mysql_upgrade can't work when the server don't start at all
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 24.11.2015 um 13:02 schrieb Carl Whalley:
I tried also the obvious, complete removal and reinstallation with the same results :-(
package removal *never ever* would touch the datadir because if it would all your data inlcuding users and permissions would be gone and i doubt that any user would want that if you are OK with lose the data because you have backups just purge the datadir at your own and run "mysql_install_db" to initalize it before restore your backups from dumpfiles reinstall packages makes no sense, that's not windows, rpm packages make sure that every file with it's correct permissions and owners exists
I see, well I kinda thought that was a long shot and backed up the mysql data dirs in case. Trouble is, the data is for a bacula installation and the irony is ... well, its not there is no backup, or that a rebuild from the tapes isn't possible, just both are a real pain (last backup too old). If there was some way to repair the current ones it would be much better. On Tue, Nov 24, 2015 at 12:28 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 13:02 schrieb Carl Whalley:
I tried also the obvious, complete removal and reinstallation with the same results :-(
package removal *never ever* would touch the datadir because if it would all your data inlcuding users and permissions would be gone and i doubt that any user would want that
if you are OK with lose the data because you have backups just purge the datadir at your own and run "mysql_install_db" to initalize it before restore your backups from dumpfiles
reinstall packages makes no sense, that's not windows, rpm packages make sure that every file with it's correct permissions and owners exists
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 24.11.2015 um 13:34 schrieb Carl Whalley:
I see, well I kinda thought that was a long shot and backed up the mysql data dirs in case. Trouble is, the data is for a bacula installation and the irony is ... well, its not there is no backup, or that a rebuild from the tapes isn't possible, just both are a real pain (last backup too old). If there was some way to repair the current ones it would be much better.
http://stackoverflow.com/questions/1708409/how-to-start-mysql-with-skip-gran... * make a local backup of your whole datadir before start * make sure that the dbserver is only reachable from localhost and stop every webserver which would try to access it * put "skip-grant-tables" into the [mysqld] section of your config * the server now likely starts because it should ignore grants * it no longer needs and password * so "mysql_upgrade" maybe suceeds and repairs the mysql-db * stop the server * remove "skip-grant-tables" * try to start it regulary
On Tue, Nov 24, 2015 at 12:28 PM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:
Am 24.11.2015 um 13:02 schrieb Carl Whalley:
I tried also the obvious, complete removal and reinstallation with the same results :-(
package removal *never ever* would touch the datadir because if it would all your data inlcuding users and permissions would be gone and i doubt that any user would want that
if you are OK with lose the data because you have backups just purge the datadir at your own and run "mysql_install_db" to initalize it before restore your backups from dumpfiles
reinstall packages makes no sense, that's not windows, rpm packages make sure that every file with it's correct permissions and owners exists
Oh boy ...well I did get the service to start this way at least, but ... [root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 10 Server version: 10.0.21-MariaDB MariaDB Server Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>MariaDB [(none)]> use mysql Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [mysql]> show tables; +---------------------------+ | Tables_in_mysql | +---------------------------+ | column_stats | | columns_priv | | db | | engine_cost | | event | | func | | general_log | | gtid_executed | | gtid_slave_pos | | help_category | | help_keyword | | help_relation | | help_topic | | host | | index_stats | | innodb_index_stats | | innodb_table_stats | | ndb_binlog_index | | plugin | | proc | | procs_priv | | proxies_priv | | roles_mapping | | server_cost | | servers | | slave_master_info | | slave_relay_log_info | | slave_worker_info | | slow_log | | table_stats | | tables_priv | | time_zone | | time_zone_leap_second | | time_zone_name | | time_zone_transition | | time_zone_transition_type | | user | +---------------------------+ 37 rows in set (0.00 sec) MariaDB [mysql]> [root@tiger etc]# mysql_upgrade Phase 1/6: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist in engine status : Operation failed mysql.event OK mysql.func OK mysql.gtid_executed Error : Table 'mysql.gtid_executed' doesn't exist in engine status : Operation failed mysql.gtid_slave_pos OK mysql.help_category Error : Table 'mysql.help_category' doesn't exist in engine status : Operation failed mysql.help_keyword Error : Table 'mysql.help_keyword' doesn't exist in engine status : Operation failed mysql.help_relation Error : Table 'mysql.help_relation' doesn't exist in engine status : Operation failed mysql.help_topic Error : Table 'mysql.help_topic' doesn't exist in engine status : Operation failed mysql.host OK mysql.index_stats OK mysql.innodb_index_stats Error : Table 'mysql.innodb_index_stats' doesn't exist in engine status : Operation failed mysql.innodb_table_stats Error : Table 'mysql.innodb_table_stats' doesn't exist in engine status : Operation failed mysql.ndb_binlog_index OK mysql.plugin Error : Table 'mysql.plugin' doesn't exist in engine status : Operation failed mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.roles_mapping OK mysql.server_cost Error : Table 'mysql.server_cost' doesn't exist in engine status : Operation failed mysql.servers Error : Table 'mysql.servers' doesn't exist in engine status : Operation failed mysql.slave_master_info Error : Table 'mysql.slave_master_info' doesn't exist in engine status : Operation failed mysql.slave_relay_log_info Error : Table 'mysql.slave_relay_log_info' doesn't exist in engine status : Operation failed mysql.slave_worker_info Error : Table 'mysql.slave_worker_info' doesn't exist in engine status : Operation failed mysql.table_stats OK mysql.tables_priv OK mysql.time_zone Error : Table 'mysql.time_zone' doesn't exist in engine status : Operation failed mysql.time_zone_leap_second Error : Table 'mysql.time_zone_leap_second' doesn't exist in engine status : Operation failed mysql.time_zone_name Error : Table 'mysql.time_zone_name' doesn't exist in engine status : Operation failed mysql.time_zone_transition Error : Table 'mysql.time_zone_transition' doesn't exist in engine status : Operation failed mysql.time_zone_transition_type Error : Table 'mysql.time_zone_transition_type' doesn't exist in engine status : Operation failed mysql.user OK Repairing tables mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist in engine status : Operation failed mysql.gtid_executed Error : Table 'mysql.gtid_executed' doesn't exist in engine status : Operation failed mysql.help_category Error : Table 'mysql.help_category' doesn't exist in engine status : Operation failed mysql.help_keyword Error : Table 'mysql.help_keyword' doesn't exist in engine status : Operation failed mysql.help_relation Error : Table 'mysql.help_relation' doesn't exist in engine status : Operation failed mysql.help_topic Error : Table 'mysql.help_topic' doesn't exist in engine status : Operation failed mysql.innodb_index_stats Error : Table 'mysql.innodb_index_stats' doesn't exist in engine status : Operation failed mysql.innodb_table_stats Error : Table 'mysql.innodb_table_stats' doesn't exist in engine status : Operation failed mysql.plugin Error : Table 'mysql.plugin' doesn't exist in engine status : Operation failed mysql.server_cost Error : Table 'mysql.server_cost' doesn't exist in engine status : Operation failed mysql.servers Error : Table 'mysql.servers' doesn't exist in engine status : Operation failed mysql.slave_master_info Error : Table 'mysql.slave_master_info' doesn't exist in engine status : Operation failed mysql.slave_relay_log_info Error : Table 'mysql.slave_relay_log_info' doesn't exist in engine status : Operation failed mysql.slave_worker_info Error : Table 'mysql.slave_worker_info' doesn't exist in engine status : Operation failed mysql.time_zone Error : Table 'mysql.time_zone' doesn't exist in engine status : Operation failed mysql.time_zone_leap_second Error : Table 'mysql.time_zone_leap_second' doesn't exist in engine status : Operation failed mysql.time_zone_name Error : Table 'mysql.time_zone_name' doesn't exist in engine status : Operation failed mysql.time_zone_transition Error : Table 'mysql.time_zone_transition' doesn't exist in engine status : Operation failed mysql.time_zone_transition_type Error : Table 'mysql.time_zone_transition_type' doesn't exist in engine status : Operation failed Phase 2/6: Fixing views sys.host_summary Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.host_summary_by_file_io OK sys.host_summary_by_file_io_type OK sys.host_summary_by_stages OK sys.host_summary_by_statement_latency OK sys.host_summary_by_statement_type OK sys.innodb_buffer_stats_by_schema OK sys.innodb_buffer_stats_by_table OK sys.innodb_lock_waits OK sys.io_by_thread_by_latency OK sys.io_global_by_file_by_bytes OK sys.io_global_by_file_by_latency OK sys.io_global_by_wait_by_bytes OK sys.io_global_by_wait_by_latency OK sys.latest_file_io OK sys.memory_by_host_by_current_bytes Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.memory_by_thread_by_current_bytes Error : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist Error : View 'sys.memory_by_thread_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.memory_by_user_by_current_bytes Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.memory_by_user_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.memory_global_by_current_bytes Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.memory_global_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.memory_global_total Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.metrics Error : Table 'performance_schema.global_status' doesn't exist Error : View 'sys.metrics' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.processlist Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.processlist' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.ps_check_lost_instrumentation Error : Table 'performance_schema.global_status' doesn't exist Error : View 'sys.ps_check_lost_instrumentation' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.schema_auto_increment_columns OK sys.schema_index_statistics OK sys.schema_object_overview OK sys.schema_redundant_indexes OK sys.schema_table_lock_waits Error : Table 'performance_schema.metadata_locks' doesn't exist Error : View 'sys.schema_table_lock_waits' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.schema_table_statistics OK sys.schema_table_statistics_with_buffer OK sys.schema_tables_with_full_table_scans OK sys.schema_unused_indexes OK sys.session Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.session_ssl_status Error : Table 'performance_schema.status_by_thread' doesn't exist Error : View 'sys.session_ssl_status' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.statement_analysis OK sys.statements_with_errors_or_warnings OK sys.statements_with_full_table_scans OK sys.statements_with_runtimes_in_95th_percentile OK sys.statements_with_sorting OK sys.statements_with_temp_tables OK sys.user_summary Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.user_summary_by_file_io OK sys.user_summary_by_file_io_type OK sys.user_summary_by_stages OK sys.user_summary_by_statement_latency OK sys.user_summary_by_statement_type OK sys.version OK sys.wait_classes_global_by_avg_latency OK sys.wait_classes_global_by_latency OK sys.waits_by_host_by_latency OK sys.waits_by_user_by_latency OK sys.waits_global_by_latency OK sys.x$host_summary Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.x$host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$host_summary_by_file_io OK sys.x$host_summary_by_file_io_type OK sys.x$host_summary_by_stages OK sys.x$host_summary_by_statement_latency OK sys.x$host_summary_by_statement_type OK sys.x$innodb_buffer_stats_by_schema OK sys.x$innodb_buffer_stats_by_table OK sys.x$innodb_lock_waits OK sys.x$io_by_thread_by_latency OK sys.x$io_global_by_file_by_bytes OK sys.x$io_global_by_file_by_latency OK sys.x$io_global_by_wait_by_bytes OK sys.x$io_global_by_wait_by_latency OK sys.x$latest_file_io OK sys.x$memory_by_host_by_current_bytes Error : Table 'performance_schema.memory_summary_by_host_by_event_name' doesn't exist Error : View 'sys.x$memory_by_host_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_by_thread_by_current_bytes Error : Table 'performance_schema.memory_summary_by_thread_by_event_name' doesn't exist Error : View 'sys.x$memory_by_thread_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_by_user_by_current_bytes Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.x$memory_by_user_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_global_by_current_bytes Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.x$memory_global_by_current_bytes' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$memory_global_total Error : Table 'performance_schema.memory_summary_global_by_event_name' doesn't exist Error : View 'sys.x$memory_global_total' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$processlist Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.x$processlist' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$ps_digest_95th_percentile_by_avg_us OK sys.x$ps_digest_avg_latency_distribution OK sys.x$ps_schema_table_statistics_io OK sys.x$schema_flattened_keys OK sys.x$schema_index_statistics OK sys.x$schema_table_lock_waits Error : Table 'performance_schema.metadata_locks' doesn't exist Error : View 'sys.x$schema_table_lock_waits' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$schema_table_statistics OK sys.x$schema_table_statistics_with_buffer OK sys.x$schema_tables_with_full_table_scans OK sys.x$session Error : Table 'performance_schema.events_transactions_current' doesn't exist Error : View 'sys.x$session' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$statement_analysis OK sys.x$statements_with_errors_or_warnings OK sys.x$statements_with_full_table_scans OK sys.x$statements_with_runtimes_in_95th_percentile OK sys.x$statements_with_sorting OK sys.x$statements_with_temp_tables OK sys.x$user_summary Error : Table 'performance_schema.memory_summary_by_user_by_event_name' doesn't exist Error : View 'sys.x$user_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them error : Corrupt sys.x$user_summary_by_file_io OK sys.x$user_summary_by_file_io_type OK sys.x$user_summary_by_stages OK sys.x$user_summary_by_statement_latency OK sys.x$user_summary_by_statement_type OK sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 3/6: Running 'mysql_fix_privilege_tables' ERROR 1932 (42S02) at line 312: Table 'mysql.plugin' doesn't exist in engine ERROR 1932 (42S02) at line 580: Table 'mysql.innodb_index_stats' doesn't exist in engine ERROR 1932 (42S02) at line 583: Table 'mysql.innodb_table_stats' doesn't exist in engine ERROR 1932 (42S02) at line 599: Table 'mysql.servers' doesn't exist in engine ERROR 1932 (42S02) at line 602: Table 'mysql.help_category' doesn't exist in engine ERROR 1932 (42S02) at line 603: Table 'mysql.help_topic' doesn't exist in engine FATAL ERROR: Upgrade failed On Tue, Nov 24, 2015 at 12:39 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 13:34 schrieb Carl Whalley:
I see, well I kinda thought that was a long shot and backed up the mysql data dirs in case. Trouble is, the data is for a bacula installation and the irony is ... well, its not there is no backup, or that a rebuild from the tapes isn't possible, just both are a real pain (last backup too old). If there was some way to repair the current ones it would be much better.
http://stackoverflow.com/questions/1708409/how-to-start-mysql-with-skip-gran...
* make a local backup of your whole datadir before start * make sure that the dbserver is only reachable from localhost and stop every webserver which would try to access it * put "skip-grant-tables" into the [mysqld] section of your config * the server now likely starts because it should ignore grants * it no longer needs and password * so "mysql_upgrade" maybe suceeds and repairs the mysql-db * stop the server * remove "skip-grant-tables" * try to start it regulary
On Tue, Nov 24, 2015 at 12:28 PM, Reindl Harald <h.reindl@thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 24.11.2015 um 13:02 schrieb Carl Whalley:
I tried also the obvious, complete removal and reinstallation with the same results :-(
package removal *never ever* would touch the datadir because if it would all your data inlcuding users and permissions would be gone and i doubt that any user would want that
if you are OK with lose the data because you have backups just purge the datadir at your own and run "mysql_install_db" to initalize it before restore your backups from dumpfiles
reinstall packages makes no sense, that's not windows, rpm packages make sure that every file with it's correct permissions and owners exists
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 24.11.2015 um 13:52 schrieb Carl Whalley:
Oh boy ...well I did get the service to start this way at least, but ...
[root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql
well, i see a lot of error i can't explain how many users do you have? i would try to purge the whole "mysql" folder after stop the service and fire "mysql_install_db" to re-create the mysql-database or even go so far to configure mysqld for a different datadir, initialize it there and replace the "mysql" folder with the so new created on any of my setups the whole "mysql" database is MyISAM and so table spaces should not matter, not sure if maraidb switched also to "innodb" as default engine in doubt drop the whole database from your current instance runnign with "skip-grant" before stop it to get rid of tablespace rferences and at least for the fresh instance "default-storage-engine = myisam" that way you should be able to merge the new created mysql-database with your current setup
This server just runs the tape backups so there are no users to worry about. I'm very out of my depth now, normally just use MySQL/Mariadb with a little admin,. never had to repair this way. Thanks again. On Tue, Nov 24, 2015 at 1:00 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 13:52 schrieb Carl Whalley:
Oh boy ...well I did get the service to start this way at least, but ...
[root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql
well, i see a lot of error i can't explain
how many users do you have?
i would try to purge the whole "mysql" folder after stop the service and fire "mysql_install_db" to re-create the mysql-database or even go so far to configure mysqld for a different datadir, initialize it there and replace the "mysql" folder with the so new created
on any of my setups the whole "mysql" database is MyISAM and so table spaces should not matter, not sure if maraidb switched also to "innodb" as default engine
in doubt drop the whole database from your current instance runnign with "skip-grant" before stop it to get rid of tablespace rferences and at least for the fresh instance "default-storage-engine = myisam"
that way you should be able to merge the new created mysql-database with your current setup
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 24.11.2015 um 14:10 schrieb Carl Whalley:
This server just runs the tape backups so there are no users to worry about. I'm very out of my depth now, normally just use MySQL/Mariadb with a little admin,. never had to repair this way.
i know it's too late, but normally before upgrades i just rsync /var/lib/mysql/ with all permissions and attributes to /var/lib/mysql-bkp/ the first time hot while the server is running, followed by stop the server, run rsync again to backup the fresh differences and get a consistent backup before doing the upgrades restore in the other direction is way faster then from external backups i still have no idea how that state coul have happened at all because F22->F23 has no version change for MariaDB, both have 10.0.x and even the F22 binaries are running unchanged after the dist-upgrade on my build/testserver before rebuild all self maintained packages P.S.: get rid of "reply-all" on mailing lists, i receive everytime your offlist copy and the message from the listserver is purged as duplicate which breaks reply-list and threading for anybody else
On Tue, Nov 24, 2015 at 1:00 PM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:
Am 24.11.2015 um 13:52 schrieb Carl Whalley:
Oh boy ...well I did get the service to start this way at least, but ...
[root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql
well, i see a lot of error i can't explain
how many users do you have?
i would try to purge the whole "mysql" folder after stop the service and fire "mysql_install_db" to re-create the mysql-database or even go so far to configure mysqld for a different datadir, initialize it there and replace the "mysql" folder with the so new created
on any of my setups the whole "mysql" database is MyISAM and so table spaces should not matter, not sure if maraidb switched also to "innodb" as default engine
in doubt drop the whole database from your current instance runnign with "skip-grant" before stop it to get rid of tablespace rferences and at least for the fresh instance "default-storage-engine = myisam"
that way you should be able to merge the new created mysql-database with your current setup
I think that maybe the MySQL installation was damaged before the OS upgrade (for instance files accidentially deleted but going un-noticed). @Carl - do you have .frm, .MYI and .MYD files for the tables that mysql_upgrade completes about? -- Peter On Tue, Nov 24, 2015 at 2:27 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 14:10 schrieb Carl Whalley:
This server just runs the tape backups so there are no users to worry about. I'm very out of my depth now, normally just use MySQL/Mariadb with a little admin,. never had to repair this way.
i know it's too late, but normally before upgrades i just rsync /var/lib/mysql/ with all permissions and attributes to /var/lib/mysql-bkp/ the first time hot while the server is running, followed by stop the server, run rsync again to backup the fresh differences and get a consistent backup before doing the upgrades
restore in the other direction is way faster then from external backups
i still have no idea how that state coul have happened at all because F22->F23 has no version change for MariaDB, both have 10.0.x and even the F22 binaries are running unchanged after the dist-upgrade on my build/testserver before rebuild all self maintained packages
P.S.: get rid of "reply-all" on mailing lists, i receive everytime your offlist copy and the message from the listserver is purged as duplicate which breaks reply-list and threading for anybody else
On Tue, Nov 24, 2015 at 1:00 PM, Reindl Harald <h.reindl@thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 24.11.2015 um 13:52 schrieb Carl Whalley:
Oh boy ...well I did get the service to start this way at least, but ...
[root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql
well, i see a lot of error i can't explain
how many users do you have?
i would try to purge the whole "mysql" folder after stop the service and fire "mysql_install_db" to re-create the mysql-database or even go so far to configure mysqld for a different datadir, initialize it there and replace the "mysql" folder with the so new created
on any of my setups the whole "mysql" database is MyISAM and so table spaces should not matter, not sure if maraidb switched also to "innodb" as default engine
in doubt drop the whole database from your current instance runnign with "skip-grant" before stop it to get rid of tablespace rferences and at least for the fresh instance "default-storage-engine = myisam"
that way you should be able to merge the new created mysql-database with your current setup
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
" .. that mysql_upgrade *complains* about", I meant. On Tue, Nov 24, 2015 at 3:01 PM, Peter Laursen <peter_laursen@webyog.com> wrote:
I think that maybe the MySQL installation was damaged before the OS upgrade (for instance files accidentially deleted but going un-noticed).
@Carl - do you have .frm, .MYI and .MYD files for the tables that mysql_upgrade completes about?
-- Peter
On Tue, Nov 24, 2015 at 2:27 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 24.11.2015 um 14:10 schrieb Carl Whalley:
This server just runs the tape backups so there are no users to worry about. I'm very out of my depth now, normally just use MySQL/Mariadb with a little admin,. never had to repair this way.
i know it's too late, but normally before upgrades i just rsync /var/lib/mysql/ with all permissions and attributes to /var/lib/mysql-bkp/ the first time hot while the server is running, followed by stop the server, run rsync again to backup the fresh differences and get a consistent backup before doing the upgrades
restore in the other direction is way faster then from external backups
i still have no idea how that state coul have happened at all because F22->F23 has no version change for MariaDB, both have 10.0.x and even the F22 binaries are running unchanged after the dist-upgrade on my build/testserver before rebuild all self maintained packages
P.S.: get rid of "reply-all" on mailing lists, i receive everytime your offlist copy and the message from the listserver is purged as duplicate which breaks reply-list and threading for anybody else
On Tue, Nov 24, 2015 at 1:00 PM, Reindl Harald <h.reindl@thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 24.11.2015 um 13:52 schrieb Carl Whalley:
Oh boy ...well I did get the service to start this way at least, but ...
[root@tiger etc]# systemctl restart mariadb.service [root@tiger tmp]# mysql
well, i see a lot of error i can't explain
how many users do you have?
i would try to purge the whole "mysql" folder after stop the service and fire "mysql_install_db" to re-create the mysql-database or even go so far to configure mysqld for a different datadir, initialize it there and replace the "mysql" folder with the so new created
on any of my setups the whole "mysql" database is MyISAM and so table spaces should not matter, not sure if maraidb switched also to "innodb" as default engine
in doubt drop the whole database from your current instance runnign with "skip-grant" before stop it to get rid of tablespace rferences and at least for the fresh instance "default-storage-engine = myisam"
that way you should be able to merge the new created mysql-database with your current setup
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
participants (3)
-
Carl Whalley
-
Peter Laursen
-
Reindl Harald