2019-03-11 16:13:52 18696 [ERROR] /usr/local/mysql/bin/mysqld: Can't find file: './db1/test11.frm' (errno: 13 - Permission denied)
2019-03-11 16:14:04 18696 [ERROR] /usr/local/mysql/bin/mysqld: Can't find file: './db1/test11.frm' (errno: 13 - Permission denied)
2019-03-11 16:14:15 18696 [Warning] InnoDB: Cannot open table db1/test11 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.
2019-03-11 16:14:21 18696 [Warning] InnoDB: Cannot open table db1/test11 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.
2019-03-11 16:19:45 18696 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown
2019-03-11 16:19:45 18696 [Note] Giving 0 client threads a chance to die gracefully
2019-03-11 16:19:45 18696 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-11 16:19:45 18696 [Note] Shutting down slave threads
2019-03-11 16:19:45 18696 [Note] Forcefully disconnecting 0 remaining clients
2019-03-11 16:19:45 18696 [Note] Binlog end
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'partition'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'ARCHIVE'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:19:45 18696 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:19:45 18696 [Note] InnoDB: FTS optimize thread exiting.
2019-03-11 16:19:45 18696 [Note] InnoDB: Starting shutdown...
2019-03-11 16:19:46 18696 [Note] InnoDB: Shutdown completed; log sequence number 1631999
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'CSV'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'CSV'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:19:46 18696 [Note] Shutting down plugin 'binlog'
2019-03-11 16:19:46 18696 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
2019-03-11 16:19:57 24069 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:19:57 24069 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:19:57 24069 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:19:57 24069 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:19:57 24069 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:19:57 24069 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:19:57 24069 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:19:57 24069 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:19:57 24069 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:19:57 24069 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:19:57 24069 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:19:57 24069 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:19:57 24069 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:19:57 24069 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:19:57 24069 [Note] InnoDB: 128 rollback segment(s) are active.
2019-03-11 16:19:57 24069 [Note] InnoDB: Waiting for purge to start
2019-03-11 16:19:57 24069 [Note] InnoDB: 5.6.38 started; log sequence number 1631999
2019-03-11 16:19:57 24069 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:19:57 24069 [Note] IPv6 is available.
2019-03-11 16:19:57 24069 [Note] IPv6 is available.
2019-03-11 16:19:57 24069 [Note] - '::' resolves to '::';
2019-03-11 16:19:57 24069 [Note] Server socket created on IP: '::'.
2019-03-11 16:19:57 24069 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:19:57 24069 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:19:57 24069 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:19:57 24069 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:19:57 24069 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:20:12 24069 [Warning] InnoDB: table tmp/test11 contains 1 user defined columns in InnoDB, but 51 columns in MySQL. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how to resolve it
2019-03-11 16:20:12 24069 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:20:16 2aee44040700 InnoDB: table "tmp"."test11"is corrupted. Please drop the table and recreate
is corrupted. Please drop the table and recreate
2019-03-11 16:20:16 24069 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:23:33 24069 [Warning] InnoDB: Cannot open table db1/test11 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.
2019-03-11 16:23:37 24069 [Warning] InnoDB: table tmp/test11 contains 1 user defined columns in InnoDB, but 51 columns in MySQL. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how to resolve it
2019-03-11 16:23:37 24069 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:23:40 2aee44040700 InnoDB: table "tmp"."test11"is corrupted. Please drop the table and recreate
2019-03-11 16:23:40 24069 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:24:10 24069 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown
2019-03-11 16:24:10 24069 [Note] Giving 0 client threads a chance to die gracefully
2019-03-11 16:24:10 24069 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-11 16:24:10 24069 [Note] Shutting down slave threads
2019-03-11 16:24:10 24069 [Note] Shutting down slave threads
2019-03-11 16:24:10 24069 [Note] Forcefully disconnecting 0 remaining clients
2019-03-11 16:24:10 24069 [Note] Binlog end
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'partition'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'ARCHIVE'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:24:10 24069 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:24:10 24069 [Note] InnoDB: FTS optimize thread exiting.
2019-03-11 16:24:10 24069 [Note] InnoDB: Starting shutdown...
2019-03-11 16:24:11 24069 [Note] InnoDB: Shutdown completed; log sequence number 1639728
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'CSV'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'CSV'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:24:11 24069 [Note] Shutting down plugin 'binlog'
2019-03-11 16:24:11 24069 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
2019-03-11 16:24:19 24940 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:24:19 24940 [Note] InnoDB: Started in read only mode
2019-03-11 16:24:19 24940 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:24:19 24940 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:24:19 24940 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:24:19 24940 [Note] InnoDB: Memory ba2019-03-11 16:24:19 24940 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:24:19 24940 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:24:19 24940 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:24:19 24940 [Note] InnoDB: Compressed tables use zlib 1.2.3
rrier is not used
2019-03-11 16:24:19 24940 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:24:19 24940 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:24:19 24940 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:24:19 24940 [Note] InnoDB: Disabling background IO write threads.
2019-03-11 16:24:19 24940 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:24:19 24940 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:24:19 24940 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:24:19 24940 [Note] InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo
2019-03-11 16:24:19 24940 [Note] InnoDB: 5.6.38 started; log sequence number 0
2019-03-11 16:24:19 24940 [Note] InnoDB: !!! innodb_force_recovery is set to 6 !!!
2019-03-11 16:24:19 24940 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:24:19 24940 [Note] IPv6 is available.
2019-03-11 16:24:19 24940 [Note] - '::' resolves to '::';
2019-03-11 16:24:19 24940 [Note] - '::' resolves to '::';
2019-03-11 16:24:19 24940 [Note] Server socket created on IP: '::'.
2019-03-11 16:24:19 24940 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:24:19 24940 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:24:19 24940 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:24:19 24940 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_master_info"' in the cache. Attempting to load the tablespace with space id 4.
2019-03-11 16:24:19 24940 [Warning] InnoDB: Allocated tablespace 4, old maximum was 0
2019-03-11 16:24:19 24940 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_worker_info"' in the cache. Attempting to load the tablespace with space id 5.
2019-03-11 16:24:19 24940 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_relay_log_info"' in the cache. Attempting to load the tablespace with space id 3.
2019-03-11 16:24:19 24940 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:24:19 24940 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:25:02 24940 [ERROR] InnoDB: Failed to find tablespace for table '"tmp"."test11"' in the cache. Attempting to load the tablespace with space id 7.
2019-03-11 16:25:02 24940 [Warning] InnoDB: table tmp/test11 contains 1 user defined columns in InnoDB, but 51 columns in MySQL. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how to resolve it
2019-03-11 16:25:02 24940 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:25:09 2ac4c6e1c700 InnoDB: table "tmp"."test11"is corrupted. Please drop the table and recreate
2019-03-11 16:25:09 24940 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:28:12 24940 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown
2019-03-11 16:28:12 24940 [Note] Giving 0 client threads a chance to die gracefully
2019-03-11 16:28:12 24940 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-11 16:28:12 24940 [Note] Shutting down slave threads
2019-03-11 16:28:12 24940 [Note] Forcefully disconnecting 0 remaining clients
2019-03-11 16:28:12 24940 [Note] Binlog end
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'partition'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'ARCHIVE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:28:12 24940 [Note] InnoDB: Starting shutdown...
2019-03-11 16:28:12 24940 [Note] InnoDB: Shutdown completed; log sequence number 8204
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'CSV'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'CSV'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:28:12 24940 [Note] Shutting down plugin 'binlog'
2019-03-11 16:28:12 24940 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
2019-03-11 16:28:19 25746 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:28:19 25746 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:28:19 25746 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:28:19 25746 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:28:19 25746 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:28:19 25746 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:28:19 25746 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:28:19 25746 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:28:19 25746 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:28:19 25746 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:28:19 25746 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:28:19 25746 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:28:19 25746 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:28:19 25746 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:28:19 25746 [Note] InnoDB: 128 rollback segment(s) are active.
2019-03-11 16:28:19 25746 [Note] InnoDB: Waiting for purge to start
2019-03-11 16:28:19 25746 [Note] InnoDB: 5.6.38 started; log sequence number 1639728
2019-03-11 16:28:19 25746 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:28:19 25746 [Note] IPv6 is available.
2019-03-11 16:28:19 25746 [Note] IPv6 is available.
2019-03-11 16:28:19 25746 [Note] - '::' resolves to '::';
2019-03-11 16:28:19 25746 [Note] Server socket created on IP: '::'.
2019-03-11 16:28:19 25746 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:28:19 25746 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:28:19 25746 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:28:19 25746 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:28:19 25746 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:28:19 25746 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:32:44 25746 [Warning] InnoDB: table tmp/test11 contains 1 user defined columns in InnoDB, but 51 columns in MySQL. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how to resolve it
2019-03-11 16:32:44 25746 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:33:57 2b99f4040700 InnoDB: table "tmp"."test11"is corrupted. Please drop the table and recreate
2019-03-11 16:33:57 25746 [Warning] InnoDB: Cannot open table tmp/test11 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.
2019-03-11 16:36:04 25746 [ERROR] Build InnoDB index translation table for Table ./tmp/test11 failed
2019-03-11 16:36:04 25746 [ERROR] Table ./tmp/test11 has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2019-03-11 16:36:04 25746 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:36:04 25746 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
08:36:04 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134280 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1e81370
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134280 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1e81370
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 2b99f403fe28 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x8f1685]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41b)[0x6563fb]
/lib64/libpthread.so.0(+0xf7e0)[0x2b99b42067e0]
/lib64/libpthread.so.0(+0xf7e0)[0x2b99b42067e0]
/usr/local/mysql/bin/mysqld[0xa2b80d]
/usr/local/mysql/bin/mysqld[0x99ce22]
/usr/local/mysql/bin/mysqld[0x99df20]
/usr/local/mysql/bin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x3e)[0x59560e]
/usr/local/mysql/bin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x66c)[0x76c27c]
/usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x1de)[0x69163e]
/usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0xef8)[0x694108]
/usr/local/mysql/bin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x48)[0x694268]
/usr/local/mysql/bin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x25)[0x70ee65]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2b6a)[0x6e4dda]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1b5)[0x6aa955]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x42)[0x6aaa02]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x12a)[0x93536a]
/lib64/libpthread.so.0(+0x7aa1)[0x2b99b41feaa1]
/lib64/libpthread.so.0(+0x7aa1)[0x2b99b41feaa1]
/lib64/libc.so.6(clone+0x6d)[0x2b99b56eebcd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2b99f8002f60): is an invalid pointer
Connection ID (thread ID): 3
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-03-11 16:36:05 26544 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:36:05 26544 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:36:05 26544 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:36:05 26544 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:36:05 26544 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:36:05 26544 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:36:05 26544 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:36:05 26544 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:36:05 26544 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:36:05 26544 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:36:05 26544 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:36:05 26544 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:36:05 26544 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:36:05 26544 [Note] InnoDB: The log sequence numbers 1639728 and 1639728 in ibdata files do not match the log sequence number 1648385 in the ib_logfiles!
2019-03-11 16:36:05 26544 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:36:05 26544 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:36:05 26544 [Note] InnoDB: Starting crash recovery.
2019-03-11 16:36:05 26544 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-03-11 16:36:05 26544 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-03-11 16:36:05 26544 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tmp/test11 uses space ID: 8 at filepath: ./tmp/test11.ibd. Cannot open tablespace db2/test which uses space ID: 8 at filepath: ./db2/test.ibd
2019-03-11 16:36:05 2b3644d79c20 InnoDB: Operating system error number 2 in a file operation.
2019-03-11 16:36:05 2b3644d79c20 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./db2/test.ibd
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./db2/test.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2019-03-11 16:36:48 27059 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:36:48 27059 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:36:48 27059 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:36:48 27059 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:36:48 27059 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:36:48 27059 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:36:48 27059 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:36:48 27059 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:36:48 27059 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:36:48 27059 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:36:48 27059 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:36:48 27059 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:36:48 27059 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:36:48 27059 [Note] InnoDB: The log sequence numbers 1639728 and 1639728 in ibdata files do not match the log sequence number 1648385 in the ib_logfiles!
2019-03-11 16:36:48 27059 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:36:48 27059 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:36:48 27059 [Note] InnoDB: Starting crash recovery.
2019-03-11 16:36:48 27059 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-03-11 16:36:48 27059 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tmp/test11 uses space ID: 8 at filepath: ./tmp/test11.ibd. Cannot open tablespace db2/test which uses space ID: 8 at filepath: ./db2/test.ibd
2019-03-11 16:36:48 2b981591ac202019-03-11 16:36:48 2b981591ac20 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./db2/test.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
InnoDB: Error: could not open single-table tablespace file ./db2/test.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
^C
You have new mail in /var/spool/mail/root
10.25.80.7:gzz3306:Master> tailf SZD-L0087668.err
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2019-03-11 16:38:32 27614 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:38:32 27614 [Note] InnoDB: Started in read only mode
2019-03-11 16:38:32 27614 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:38:32 27614 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:38:32 27614 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:38:32 27614 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:38:32 27614 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:38:32 27614 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:38:32 27614 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:38:32 27614 [Note] InnoDB: Disabling background IO write threads.
2019-03-11 16:38:32 27614 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:38:32 27614 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:38:32 27614 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:38:32 27614 [Note] InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo
2019-03-11 16:38:32 27614 [Note] InnoDB: 5.6.38 started; log sequence number 0
2019-03-11 16:38:32 27614 [Note] InnoDB: !!! innodb_force_recovery is set to 6 !!!
2019-03-11 16:38:32 27614 [Note] Recovering after a crash using /var/mysql/data3306/log/mysql-bin
2019-03-11 16:38:32 27614 [Note] Starting crash recovery...
2019-03-11 16:38:32 27614 [Note] Crash recovery finished.
2019-03-11 16:38:32 27614 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:38:32 27614 [Note] IPv6 is available.
2019-03-11 16:38:32 27614 [Note] - '::' resolves to '::';
2019-03-11 16:38:32 27614 [Note] Server socket created on IP: '::'.
2019-03-11 16:38:32 27614 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:38:32 27614 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:38:32 27614 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:38:32 27614 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_master_info"' in the cache. Attempting to load the tablespace with space id 4.
2019-03-11 16:38:32 27614 [Warning] InnoDB: Allocated tablespace 4, old maximum was 0
2019-03-11 16:38:32 27614 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_worker_info"' in the cache. Attempting to load the tablespace with space id 5.
2019-03-11 16:38:32 27614 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_relay_log_info"' in the cache. Attempting to load the tablespace with space id 3.
2019-03-11 16:38:32 27614 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:38:32 27614 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:38:44 27614 [ERROR] InnoDB: Failed to find tablespace for table '"tmp"."test11"' in the cache. Attempting to load the tablespace with space id 8.
2019-03-11 16:38:44 27614 [ERROR] Build InnoDB index translation table for Table ./tmp/test11 failed
2019-03-11 16:38:44 27614 [ERROR] Table ./tmp/test11 has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2019-03-11 16:38:44 27614 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:38:44 27614 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:38:44 27614 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:38:44 27614 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:41:52 27614 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:41:52 27614 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:41:52 27614 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:41:52 27614 [ERROR] Build InnoDB index translation table for Table ./tmp/test11 failed
2019-03-11 16:41:52 27614 [ERROR] Table ./tmp/test11 has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2019-03-11 16:41:52 27614 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:41:52 27614 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:41:52 27614 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:41:52 27614 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:43:26 27614 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:43:26 27614 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:43:26 27614 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:44:10 27614 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown
2019-03-11 16:44:10 27614 [Note] Giving 0 client threads a chance to die gracefully
2019-03-11 16:44:10 27614 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-11 16:44:10 27614 [Note] Shutting down slave threads
2019-03-11 16:44:10 27614 [Note] Forcefully disconnecting 0 remaining clients
2019-03-11 16:44:10 27614 [Note] Binlog end
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'partition'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'ARCHIVE'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:44:10 27614 [Note] InnoDB: Starting shutdown...
2019-03-11 16:44:10 27614 [Note] InnoDB: Shutdown completed; log sequence number 8204
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'CSV'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:44:10 27614 [Note] Shutting down plugin 'binlog'
2019-03-11 16:44:10 27614 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
2019-03-11 16:44:33 28608 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:44:33 28608 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:44:33 28608 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:44:33 28608 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:44:33 28608 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:44:33 28608 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:44:33 28608 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:44:33 28608 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:44:33 28608 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:44:33 28608 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:44:33 28608 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:44:33 28608 [Note] InnoDB: The log sequence numbers 1639728 and 1639728 in ibdata files do not match the log sequence number 1648385 in the ib_logfiles!
2019-03-11 16:44:33 28608 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:44:33 28608 [Note] InnoDB: Starting crash recovery.
2019-03-11 16:44:33 28608 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-03-11 16:44:33 28608 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tmp/test11 uses space ID: 8 at filepath: ./tmp/test11.ibd. Cannot open tablespace db2/test which uses space ID: 8 at filepath: ./db2/test.ibd
2019-03-11 16:44:33 2b2acc6ddc20 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./db2/test.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2019-03-11 16:46:55 29289 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:46:55 29289 [Note] InnoDB: Started in read only mode
2019-03-11 16:46:55 29289 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:46:55 29289 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:46:55 29289 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:46:55 29289 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:46:55 29289 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:46:55 29289 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:46:55 29289 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:46:55 29289 [Note] InnoDB: Disabling background IO write threads.
2019-03-11 16:46:55 29289 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:46:55 29289 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:46:55 29289 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:46:55 29289 [Note] InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo
2019-03-11 16:46:55 29289 [Note] InnoDB: 5.6.38 started; log sequence number 0
2019-03-11 16:46:55 29289 [Note] InnoDB: !!! innodb_force_recovery is set to 6 !!!
2019-03-11 16:46:55 29289 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:46:55 29289 [Note] IPv6 is available.
2019-03-11 16:46:55 29289 [Note] - '::' resolves to '::';
2019-03-11 16:46:55 29289 [Note] Server socket created on IP: '::'.
2019-03-11 16:46:55 29289 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:46:55 29289 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:46:55 29289 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:46:55 29289 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_master_info"' in the cache. Attempting to load the tablespace with space id 4.
2019-03-11 16:46:55 29289 [Warning] InnoDB: Allocated tablespace 4, old maximum was 0
2019-03-11 16:46:55 29289 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_worker_info"' in the cache. Attempting to load the tablespace with space id 5.
2019-03-11 16:46:55 29289 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."slave_relay_log_info"' in the cache. Attempting to load the tablespace with space id 3.
2019-03-11 16:46:55 29289 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:46:55 29289 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:47:01 29289 [ERROR] InnoDB: Failed to find tablespace for table '"tmp"."test11"' in the cache. Attempting to load the tablespace with space id 8.
2019-03-11 16:47:01 29289 [ERROR] Build InnoDB index translation table for Table ./tmp/test11 failed
2019-03-11 16:47:01 29289 [ERROR] Table ./tmp/test11 has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2019-03-11 16:47:01 29289 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:47:01 29289 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:47:01 29289 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:47:01 29289 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:47:01 29289 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:47:22 29289 [ERROR] Build InnoDB index translation table for Table ./tmp/test11 failed
2019-03-11 16:47:22 29289 [ERROR] Table ./tmp/test11 has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.
2019-03-11 16:47:22 29289 [Warning] Table ./tmp/test11 key_used_on_scan is 0 even though there is no primary key inside InnoDB.
2019-03-11 16:47:22 29289 [ERROR] InnoDB: Table tmp/test11 contains 0 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MySQL
2019-03-11 16:47:22 29289 [ERROR] Innodb could not find key n:o 0 with name PRIMARY from dict cache for table tmp/test11
2019-03-11 16:47:22 29289 [ERROR] Table tmp/test11 contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:49:16 29289 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown
2019-03-11 16:49:16 29289 [Note] Giving 0 client threads a chance to die gracefully
2019-03-11 16:49:16 29289 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-11 16:49:16 29289 [Note] Shutting down slave threads
2019-03-11 16:49:16 29289 [Note] Forcefully disconnecting 0 remaining clients
2019-03-11 16:49:16 29289 [Note] Binlog end
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'partition'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'ARCHIVE'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_METRICS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMPMEM'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_CMP'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_LOCKS'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'INNODB_TRX'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'InnoDB'
2019-03-11 16:49:16 29289 [Note] InnoDB: Starting shutdown...
2019-03-11 16:49:16 29289 [Note] InnoDB: Shutdown completed; log sequence number 8204
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'BLACKHOLE'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'CSV'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'MyISAM'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'MRG_MYISAM'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'MEMORY'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'sha256_password'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'mysql_old_password'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'mysql_native_password'
2019-03-11 16:49:16 29289 [Note] Shutting down plugin 'binlog'
2019-03-11 16:49:16 29289 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
2019-03-11 16:49:23 29906 [Note] Plugin 'FEDERATED' is disabled.
2019-03-11 16:49:23 29906 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-03-11 16:49:23 29906 [Note] InnoDB: The InnoDB memory heap is disabled
2019-03-11 16:49:23 29906 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-11 16:49:23 29906 [Note] InnoDB: Memory barrier is not used
2019-03-11 16:49:23 29906 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-11 16:49:23 29906 [Note] InnoDB: Using Linux native AIO
2019-03-11 16:49:23 29906 [Note] InnoDB: Using CPU crc32 instructions
2019-03-11 16:49:23 29906 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-03-11 16:49:23 29906 [Note] InnoDB: Completed initialization of buffer pool
2019-03-11 16:49:24 29906 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-11 16:49:24 29906 [Note] InnoDB: The log sequence numbers 1639728 and 1639728 in ibdata files do not match the log sequence number 1648385 in the ib_logfiles!
2019-03-11 16:49:24 29906 [Note] InnoDB: Database was not shutdown normally!
2019-03-11 16:49:24 29906 [Note] InnoDB: Starting crash recovery.
2019-03-11 16:49:24 29906 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-03-11 16:49:24 29906 [Note] InnoDB: Restoring possible half-written data pages
2019-03-11 16:49:24 29906 [Note] InnoDB: from the doublewrite buffer...
2019-03-11 16:49:24 2b389b9cac20 InnoDB: Error: table 'tmp/test11'
InnoDB: in InnoDB data dictionary has tablespace id 8,
InnoDB: but the tablespace with that id has name db2/test.
InnoDB: Have you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2019-03-11 16:49:24 29906 [Note] InnoDB: 128 rollback segment(s) are active.
2019-03-11 16:49:24 29906 [Note] InnoDB: Waiting for purge to start
2019-03-11 16:49:24 29906 [Note] InnoDB: 5.6.38 started; log sequence number 1648385
2019-03-11 16:49:24 29906 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-11 16:49:24 29906 [Note] IPv6 is available.
2019-03-11 16:49:24 29906 [Note] - '::' resolves to '::';
2019-03-11 16:49:24 29906 [Note] Server socket created on IP: '::'.
2019-03-11 16:49:24 29906 [Warning] 'user' entry 'hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:49:24 29906 [Warning] 'db' entry 'hive_metadata hive@spark1' ignored in --skip-name-resolve mode.
2019-03-11 16:49:24 29906 [Warning] 'proxies_priv' entry '@ root@szd-l0087668' ignored in --skip-name-resolve mode.
2019-03-11 16:49:24 29906 [Note] Event Scheduler: Loaded 0 events
2019-03-11 16:49:24 29906 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:49:24 29906 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.38-log' socket: '/var/mysql/data3306/mysql.sock' port: 3306 Source distribution
2019-03-11 16:49:33 29906 [Warning] InnoDB: Cannot open table db1/test11 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.
2019-03-11 16:49:43 29906 [Warning] InnoDB: Cannot open table db1/test11 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.
2019-03-11 16:50:06 2b38d8040700 InnoDB: Error: table `db1`.`test11` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 16:51:58 2b38d8040700 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2019-03-11 16:51:58 29906 [ERROR] InnoDB: Cannot create file './db1/test11.ibd'
2019-03-11 16:51:58 29906 [ERROR] InnoDB: The file './db1/test11.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './db1/test11.ibd' under the 'datadir' of MySQL.
2019-03-11 16:55:34 29906 [Warning] InnoDB: Tablespace 'db1/test11' exists in the cache with id 98 != 100
2019-03-11 16:55:34 29906 [Warning] InnoDB: Freeing existing tablespace 'db1/test11' entry from the cache with id 100
2019-03-11 17:03:44 29906 [Note] InnoDB: Sync to disk
2019-03-11 17:03:45 29906 [Note] InnoDB: Sync to disk - done!
2019-03-11 17:03:45 29906 [Note] InnoDB: Phase I - Update all pages
2019-03-11 17:03:45 29906 [Note] InnoDB: Phase I - Update all pages
2019-03-11 17:04:12 29906 [Note] InnoDB: Sync to disk
2019-03-11 17:04:13 29906 [Note] InnoDB: Sync to disk - done!
2019-03-11 17:04:13 29906 [Note] InnoDB: Phase III - Flush changes to disk
2019-03-11 17:04:14 29906 [Note] InnoDB: Phase IV - Flush complete
2019-03-11 17:13:27 29906 [Warning] InnoDB: Cannot open table sakila/actor 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.
2019-03-11 17:13:31 29906 [Warning] InnoDB: Cannot open table sakila/actor 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.
2019-03-11 17:13:54 2b38d8040700 InnoDB: Error: table `sakila`.`actor` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 17:14:51 29906 [Warning] InnoDB: Tablespace 'sakila/actor' exists in the cache with id 7 != 101
2019-03-11 17:14:51 29906 [Warning] InnoDB: Freeing existing tablespace 'sakila/actor' entry from the cache with id 101
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/a 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/b 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/t 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/t1 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/t2 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/t3 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.
2019-03-11 17:44:41 29906 [Warning] InnoDB: Cannot open table db2/test 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.
2019-03-11 17:44:49 29906 [Warning] InnoDB: Cannot open table db2/t1 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.
2019-03-11 17:45:37 29906 [Warning] InnoDB: Cannot open table db2/t1 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.
2019-03-11 17:47:19 2b38e4040700 InnoDB: Error: table `db2`.`t1` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/a 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.
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/b 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.
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/t 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.
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/t2 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.
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/t3 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.
2019-03-11 17:48:15 29906 [Warning] InnoDB: Cannot open table db2/test 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.
2019-03-11 17:48:26 2b38e4040700 InnoDB: Operating system error number 17 in a file operation.
InnoDB: Error number 17 means 'File exists'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2019-03-11 17:48:26 29906 [ERROR] InnoDB: Cannot create file './db2/t1.ibd'
2019-03-11 17:48:26 29906 [ERROR] InnoDB: The file './db2/t1.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './db2/t1.ibd' under the 'datadir' of MySQL.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/a 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.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/b 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.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/t 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.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/t2 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.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/t3 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.
2019-03-11 17:51:16 29906 [Warning] InnoDB: Cannot open table db2/test 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.
2019-03-11 17:51:18 29906 [Warning] InnoDB: Cannot open table db2/t2 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.
err
發表評論
所有評論
還沒有人評論，想成為第一個評論的人麼? 請在上方評論欄輸入並且點擊發布.
相關文章