Feb 2 13:15:57 tx mysqld: 150202 13:15:57 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 13:15:57 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 13:15:57 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 13:15:57 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 13:15:57 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 13:15:57 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 13:15:57 tx mysqld: doesn't support. Feb 2 13:15:57 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 13:15:57 tx mysqld: how you can resolve the problem. Feb 2 13:15:57 tx mysqld: Feb 2 13:17:28 tx mysqld: 150202 13:17:28 InnoDB: Error: table `atest_sn5`.`dashboard` does not exist in the InnoDB internal Feb 2 13:17:28 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 13:17:28 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 13:17:28 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 13:17:28 tx mysqld: InnoDB: You can look for further help from Feb 2 13:17:28 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 13:17:58 tx mysqld: 150202 13:17:58 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 13:17:58 tx mysqld: Feb 2 13:17:58 tx mysqld: 150202 13:17:58 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 13:17:58 tx mysqld: 150202 13:17:58 InnoDB: Starting shutdown... Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Shutdown completed; log sequence number 72512631064 Feb 2 13:17:59 tx mysqld: 150202 13:17:59 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 13:17:59 tx mysqld: Feb 2 13:17:59 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: The InnoDB memory heap is disabled Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Using Linux native AIO Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: Completed initialization of buffer pool Feb 2 13:17:59 tx mysqld: 150202 13:17:59 InnoDB: highest supported file format is Barracuda. Feb 2 13:17:59 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 13:18:04 tx mysqld: 150202 13:18:04 InnoDB: Waiting for the background threads to start Feb 2 13:18:05 tx mysqld: 150202 13:18:05 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 72512631064 Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [ERROR] Function 'ARCHIVE' already exists Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [ERROR] Function 'FEDERATED' already exists Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [ERROR] Function 'BLACKHOLE' already exists Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 13:18:05 tx mysqld: 150202 13:18:05 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 13:18:06 tx mysqld: 150202 13:18:06 [Note] Event Scheduler: Loaded 0 events Feb 2 13:18:06 tx mysqld: 150202 13:18:06 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 13:18:06 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 13:18:06 tx /etc/mysql/debian-start[23003]: Upgrading MySQL tables if necessary. Feb 2 13:18:06 tx /etc/mysql/debian-start[23006]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 13:18:06 tx /etc/mysql/debian-start[23006]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 13:18:06 tx /etc/mysql/debian-start[23006]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 13:18:06 tx /etc/mysql/debian-start[23006]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 13:18:06 tx /etc/mysql/debian-start[23017]: Checking for insecure root accounts. Feb 2 13:18:06 tx /etc/mysql/debian-start[23022]: Triggering myisam-recover for all MyISAM tables Feb 2 13:18:31 tx mysqld: 150202 13:18:31 [Warning] Aborted connection 84 to db: 'atest_sn' user: 'q' host: 'localhost' (Unknown error) Feb 2 13:44:47 tx mysqld: 150202 13:44:47 InnoDB: Error: in ALTER TABLE `atest_sn5`.`cities` Feb 2 13:44:47 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 13:44:47 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 13:44:59 tx mysqld: 150202 13:44:59 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 13:44:59 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 13:44:59 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 13:47:55 tx mysqld: 150202 13:47:55 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 13:47:55 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 13:47:55 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 13:59:53 tx mysqld: 150202 13:59:53 [Warning] Aborted connection 115 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 14:18:44 tx mysqld: 150202 14:18:44 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 14:18:44 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:18:44 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:20:19 tx mysqld: 150202 14:20:19 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 14:20:19 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:20:19 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:20:52 tx mysqld: 150202 14:20:52 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 14:20:52 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:20:52 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:26:26 tx mysqld: 150202 14:26:26 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:26:26 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:26:26 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:26:58 tx mysqld: 150202 14:26:58 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:26:58 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:26:58 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:27:17 tx mysqld: 150202 14:27:17 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:27:17 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:27:17 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:27:29 tx mysqld: 150202 14:27:29 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:27:29 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:27:29 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:27:53 tx mysqld: 150202 14:27:53 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:27:53 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:27:53 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:28:31 tx mysqld: 150202 14:28:31 InnoDB: Error: in ALTER TABLE `atest_sn5`.`profiles` Feb 2 14:28:31 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:28:31 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:36:32 tx mysqld: 150202 14:36:32 [Warning] Aborted connection 209 to db: 'atest_sn' user: 'q' host: 'localhost' (Unknown error) Feb 2 14:45:38 tx mysqld: 150202 14:45:38 [Warning] Aborted connection 195 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 14:46:18 tx mysqld: 150202 14:46:18 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 14:46:18 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:46:18 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 14:46:20 tx mysqld: 150202 14:46:20 [Warning] Aborted connection 148 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 14:49:57 tx mysqld: 150202 14:49:57 InnoDB: Error: in ALTER TABLE `atest_sn5`.`servicegroups_services` Feb 2 14:49:57 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 14:49:57 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 15:14:43 tx mysqld: 150202 15:14:43 [Warning] Aborted connection 302 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 15:18:16 tx mysqld: 150202 15:18:16 [Warning] Aborted connection 305 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 15:32:55 tx mysqld: 150202 15:32:55 [Warning] Aborted connection 234 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 15:43:38 tx mysqld: 150202 15:43:38 [Warning] Aborted connection 401 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 16:10:35 tx mysqld: 150202 16:10:35 InnoDB: Error: in ALTER TABLE `atest_sn5`.`users_address_cash` Feb 2 16:10:35 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 16:10:35 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 16:12:56 tx mysqld: 150202 16:12:56 InnoDB: Error: in ALTER TABLE `atest_sn5`.`users` Feb 2 16:12:56 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 16:12:56 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 16:16:11 tx mysqld: 150202 16:16:11 InnoDB: Error: in ALTER TABLE `atest_sn5`.`users` Feb 2 16:16:11 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 16:16:11 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 16:32:39 tx mysqld: 150202 16:32:39 InnoDB: Error: in ALTER TABLE `atest_sn5`.`users` Feb 2 16:32:39 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 16:32:39 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 16:32:49 tx mysqld: 150202 16:32:49 InnoDB: Error: in ALTER TABLE `atest_sn5`.`users` Feb 2 16:32:49 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 16:32:49 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 16:34:49 tx mysqld: 150202 16:34:49 [Warning] Aborted connection 494 to db: 'atest_sn' user: 'q' host: 'localhost' (Unknown error) Feb 2 16:43:48 tx mysqld: 150202 16:43:48 [Warning] Aborted connection 526 to db: 'atest_sn' user: 'q' host: 'localhost' (Unknown error) Feb 2 16:45:55 tx mysqld: 150202 16:45:55 [Warning] Aborted connection 409 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 17:14:58 tx mysqld: 150202 17:14:58 [Warning] Aborted connection 549 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 17:20:40 tx mysqld: 150202 17:20:40 InnoDB: Error: in ALTER TABLE `atest_sn5`.`old_newspapers_booked` Feb 2 17:20:40 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 17:20:40 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 17:20:40 tx mysqld: 150202 17:20:40 InnoDB: Error: in ALTER TABLE `atest_sn5`.`old_products_booked` Feb 2 17:20:40 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 17:20:40 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 17:32:16 tx mysqld: 150202 17:32:16 [ERROR] mysqld got signal 11 ; Feb 2 17:32:16 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 17:32:16 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 17:32:16 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 17:32:16 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 17:32:16 tx mysqld: something is definitely wrong and this may fail. Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 17:32:16 tx mysqld: key_buffer_size=134217728 Feb 2 17:32:16 tx mysqld: read_buffer_size=2097152 Feb 2 17:32:16 tx mysqld: max_used_connections=6 Feb 2 17:32:16 tx mysqld: max_threads=102 Feb 2 17:32:16 tx mysqld: thread_count=2 Feb 2 17:32:16 tx mysqld: It is possible that mysqld could use up to Feb 2 17:32:16 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 17:32:16 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: Thread pointer: 0x0x7fa828360000 Feb 2 17:32:16 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 17:32:16 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 17:32:16 tx mysqld: terribly wrong... Feb 2 17:32:16 tx mysqld: stack_bottom = 0x7fa8596c6e40 thread_stack 0x48000 Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fa85a15270e] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7fa859d442d7] Feb 2 17:32:16 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa858df3340] Feb 2 17:32:16 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7fa857f1bda6] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7fa85a099ecd] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7fa85a0002a1] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7fa85a005c25] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7fa859f73258] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7fa859f5288f] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7fa859d4b027] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7fa859d4ba3c] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7fa859cae89f] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7fa859c79c72] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7fa859c7a87f] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7fa859c03656] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7fa859c03cea] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7fa859c05ebd] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7fa859cc3663] Feb 2 17:32:16 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7fa859cc375a] Feb 2 17:32:16 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fa858deb182] Feb 2 17:32:16 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa857ed600d] Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: Trying to get some variables. Feb 2 17:32:16 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 17:32:16 tx mysqld: Query (0x7fa81c01f018): is an invalid pointer Feb 2 17:32:16 tx mysqld: Connection ID (thread ID): 619 Feb 2 17:32:16 tx mysqld: Status: NOT_KILLED Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 17:32:16 tx mysqld: Feb 2 17:32:16 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 17:32:16 tx mysqld: information that should help you find out what is causing the crash. Feb 2 17:32:17 tx mysqld_safe: Number of processes running now: 0 Feb 2 17:32:17 tx mysqld_safe: mysqld restarted Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: The InnoDB memory heap is disabled Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Using Linux native AIO Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Completed initialization of buffer pool Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: highest supported file format is Barracuda. Feb 2 17:32:17 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 84575057100 Feb 2 17:32:17 tx mysqld: 150202 17:32:17 InnoDB: Database was not shut down normally! Feb 2 17:32:17 tx mysqld: InnoDB: Starting crash recovery. Feb 2 17:32:17 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 17:32:20 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 17:32:20 tx mysqld: InnoDB: buffer... Feb 2 17:32:24 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 84575087525 Feb 2 17:32:27 tx mysqld: 150202 17:32:27 InnoDB: Starting an apply batch of log records to the database... Feb 2 17:32:28 tx mysqld: InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 17:32:28 tx mysqld: InnoDB: Apply batch completed Feb 2 17:32:28 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 17:32:28 tx mysqld: 150202 17:32:28 InnoDB: Waiting for the background threads to start Feb 2 17:32:29 tx mysqld: 150202 17:32:29 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84575087525 Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [ERROR] Function 'ARCHIVE' already exists Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [ERROR] Function 'FEDERATED' already exists Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [ERROR] Function 'BLACKHOLE' already exists Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Note] Event Scheduler: Loaded 0 events Feb 2 17:32:29 tx mysqld: 150202 17:32:29 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 17:32:29 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 17:32:43 tx mysqld: 150202 17:32:43 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 17:32:43 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:32:43 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:32:43 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:32:43 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:32:43 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:32:43 tx mysqld: doesn't support. Feb 2 17:32:43 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:32:43 tx mysqld: how you can resolve the problem. Feb 2 17:32:43 tx mysqld: Feb 2 17:32:43 tx mysqld: 150202 17:32:43 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 17:32:43 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:32:43 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:32:43 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:32:43 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:32:43 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:32:43 tx mysqld: doesn't support. Feb 2 17:32:43 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:32:43 tx mysqld: how you can resolve the problem. Feb 2 17:32:43 tx mysqld: Feb 2 17:32:44 tx mysqld: 150202 17:32:44 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 17:32:44 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:32:44 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:32:44 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:32:44 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:32:44 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:32:44 tx mysqld: doesn't support. Feb 2 17:32:44 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:32:44 tx mysqld: how you can resolve the problem. Feb 2 17:32:44 tx mysqld: Feb 2 17:33:44 tx mysqld: 150202 17:33:44 [ERROR] mysqld got signal 11 ; Feb 2 17:33:44 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 17:33:44 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 17:33:44 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 17:33:44 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 17:33:44 tx mysqld: something is definitely wrong and this may fail. Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 17:33:44 tx mysqld: key_buffer_size=134217728 Feb 2 17:33:44 tx mysqld: read_buffer_size=2097152 Feb 2 17:33:44 tx mysqld: max_used_connections=1 Feb 2 17:33:44 tx mysqld: max_threads=102 Feb 2 17:33:44 tx mysqld: thread_count=1 Feb 2 17:33:44 tx mysqld: It is possible that mysqld could use up to Feb 2 17:33:44 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 17:33:44 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: Thread pointer: 0x0x7f076f7a0000 Feb 2 17:33:44 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 17:33:44 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 17:33:44 tx mysqld: terribly wrong... Feb 2 17:33:44 tx mysqld: stack_bottom = 0x7f07a0c10e40 thread_stack 0x48000 Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f07a157870e] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f07a116a2d7] Feb 2 17:33:44 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f07a0219340] Feb 2 17:33:44 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7f079f341da6] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7f07a14bfecd] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7f07a14262a1] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7f07a142bc25] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7f07a1399258] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7f07a137888f] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7f07a1171027] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7f07a1171a3c] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7f07a10d489f] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7f07a109fc72] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7f07a10a087f] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7f07a1029656] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7f07a1029cea] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7f07a102bebd] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7f07a10e9663] Feb 2 17:33:44 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7f07a10e975a] Feb 2 17:33:44 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f07a0211182] Feb 2 17:33:44 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f079f2fc00d] Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: Trying to get some variables. Feb 2 17:33:44 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 17:33:44 tx mysqld: Query (0x7f076a021018): is an invalid pointer Feb 2 17:33:44 tx mysqld: Connection ID (thread ID): 8 Feb 2 17:33:44 tx mysqld: Status: NOT_KILLED Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 17:33:44 tx mysqld: Feb 2 17:33:44 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 17:33:44 tx mysqld: information that should help you find out what is causing the crash. Feb 2 17:33:44 tx mysqld_safe: Number of processes running now: 0 Feb 2 17:33:44 tx mysqld_safe: mysqld restarted Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: The InnoDB memory heap is disabled Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Using Linux native AIO Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Completed initialization of buffer pool Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: highest supported file format is Barracuda. Feb 2 17:33:44 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 84618369652 Feb 2 17:33:44 tx mysqld: 150202 17:33:44 InnoDB: Database was not shut down normally! Feb 2 17:33:44 tx mysqld: InnoDB: Starting crash recovery. Feb 2 17:33:44 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 17:33:44 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 17:33:44 tx mysqld: InnoDB: buffer... Feb 2 17:33:49 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 84618380407 Feb 2 17:33:58 tx mysqld: 150202 17:33:58 InnoDB: Starting an apply batch of log records to the database... Feb 2 17:33:59 tx mysqld: InnoDB: Progress in percents: 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 17:33:59 tx mysqld: InnoDB: Apply batch completed Feb 2 17:33:59 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 17:34:00 tx mysqld: 150202 17:34:00 InnoDB: Waiting for the background threads to start Feb 2 17:34:01 tx mysqld: 150202 17:34:01 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84618380407 Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [ERROR] Function 'ARCHIVE' already exists Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [ERROR] Function 'FEDERATED' already exists Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [ERROR] Function 'BLACKHOLE' already exists Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Note] Event Scheduler: Loaded 0 events Feb 2 17:34:01 tx mysqld: 150202 17:34:01 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 17:34:01 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 17:34:09 tx mysqld: 150202 17:34:09 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:34:09 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:34:09 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:34:09 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:34:09 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:34:09 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:34:09 tx mysqld: doesn't support. Feb 2 17:34:09 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:34:09 tx mysqld: how you can resolve the problem. Feb 2 17:34:09 tx mysqld: Feb 2 17:34:32 tx mysqld: 150202 17:34:32 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:34:32 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:34:32 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:34:32 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:34:32 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:34:32 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:34:32 tx mysqld: doesn't support. Feb 2 17:34:32 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:34:32 tx mysqld: how you can resolve the problem. Feb 2 17:34:32 tx mysqld: Feb 2 17:34:53 tx mysqld: 150202 17:34:53 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:34:53 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:34:53 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:34:53 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:34:53 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:34:53 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:34:53 tx mysqld: doesn't support. Feb 2 17:34:53 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:34:53 tx mysqld: how you can resolve the problem. Feb 2 17:34:53 tx mysqld: Feb 2 17:35:11 tx mysqld: 150202 17:35:11 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:35:11 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:35:11 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:35:11 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:35:11 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:35:11 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:35:11 tx mysqld: doesn't support. Feb 2 17:35:11 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:35:11 tx mysqld: how you can resolve the problem. Feb 2 17:35:11 tx mysqld: Feb 2 17:35:33 tx mysqld: 150202 17:35:33 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:35:33 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:35:33 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:35:33 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:35:33 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:35:33 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:35:33 tx mysqld: doesn't support. Feb 2 17:35:33 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:35:33 tx mysqld: how you can resolve the problem. Feb 2 17:35:33 tx mysqld: Feb 2 17:36:13 tx mysqld: 150202 17:36:13 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:36:13 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:36:13 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:36:13 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:36:13 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:36:13 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:36:13 tx mysqld: doesn't support. Feb 2 17:36:13 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:36:13 tx mysqld: how you can resolve the problem. Feb 2 17:36:13 tx mysqld: Feb 2 17:36:50 tx mysqld: 150202 17:36:50 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:36:50 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:36:50 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:36:50 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:36:50 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:36:50 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:36:50 tx mysqld: doesn't support. Feb 2 17:36:50 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:36:50 tx mysqld: how you can resolve the problem. Feb 2 17:36:50 tx mysqld: Feb 2 17:37:08 tx mysqld: 150202 17:37:08 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:37:08 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:08 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:08 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:08 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:08 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:08 tx mysqld: doesn't support. Feb 2 17:37:08 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:08 tx mysqld: how you can resolve the problem. Feb 2 17:37:08 tx mysqld: Feb 2 17:37:14 tx mysqld: 150202 17:37:14 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:37:14 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:14 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:14 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:14 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:14 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:14 tx mysqld: doesn't support. Feb 2 17:37:14 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:14 tx mysqld: how you can resolve the problem. Feb 2 17:37:14 tx mysqld: Feb 2 17:37:27 tx mysqld: 150202 17:37:27 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:37:27 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:27 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:27 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:27 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:27 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:27 tx mysqld: doesn't support. Feb 2 17:37:27 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:27 tx mysqld: how you can resolve the problem. Feb 2 17:37:27 tx mysqld: Feb 2 17:37:40 tx mysqld: 150202 17:37:40 [Warning] Access denied for user 'root'@'localhost' (using password: NO) Feb 2 17:37:47 tx mysqld: 150202 17:37:47 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:37:47 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:47 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:47 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:47 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:47 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:47 tx mysqld: doesn't support. Feb 2 17:37:47 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:47 tx mysqld: how you can resolve the problem. Feb 2 17:37:47 tx mysqld: Feb 2 17:37:48 tx mysqld: 150202 17:37:48 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:37:48 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:48 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:48 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:48 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:48 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:48 tx mysqld: doesn't support. Feb 2 17:37:48 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:48 tx mysqld: how you can resolve the problem. Feb 2 17:37:48 tx mysqld: Feb 2 17:37:54 tx mysqld: 150202 17:37:54 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 17:37:54 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:37:54 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:37:54 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:37:54 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:37:54 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:37:54 tx mysqld: doesn't support. Feb 2 17:37:54 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:37:54 tx mysqld: how you can resolve the problem. Feb 2 17:37:54 tx mysqld: Feb 2 17:38:18 tx mysqld: 150202 17:38:18 [ERROR] mysqld got signal 11 ; Feb 2 17:38:18 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 17:38:18 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 17:38:18 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 17:38:18 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 17:38:18 tx mysqld: something is definitely wrong and this may fail. Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 17:38:18 tx mysqld: key_buffer_size=134217728 Feb 2 17:38:18 tx mysqld: read_buffer_size=2097152 Feb 2 17:38:18 tx mysqld: max_used_connections=3 Feb 2 17:38:18 tx mysqld: max_threads=102 Feb 2 17:38:18 tx mysqld: thread_count=3 Feb 2 17:38:18 tx mysqld: It is possible that mysqld could use up to Feb 2 17:38:18 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 17:38:18 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: Thread pointer: 0x0x7f697dfed000 Feb 2 17:38:18 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 17:38:18 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 17:38:18 tx mysqld: terribly wrong... Feb 2 17:38:18 tx mysqld: stack_bottom = 0x7f69af24be40 thread_stack 0x48000 Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f69afc4570e] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f69af8372d7] Feb 2 17:38:18 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f69ae8e6340] Feb 2 17:38:18 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7f69ada0eda6] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7f69afb8cecd] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7f69afaf32a1] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7f69afaf8c25] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7f69afa66258] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7f69afa4588f] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7f69af83e027] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7f69af83ea3c] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7f69af7a189f] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7f69af76cc72] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7f69af76d87f] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7f69af6f6656] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7f69af6f6cea] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7f69af6f8ebd] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7f69af7b6663] Feb 2 17:38:18 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7f69af7b675a] Feb 2 17:38:18 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f69ae8de182] Feb 2 17:38:18 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f69ad9c900d] Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: Trying to get some variables. Feb 2 17:38:18 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 17:38:18 tx mysqld: Query (0x7f697901f018): is an invalid pointer Feb 2 17:38:18 tx mysqld: Connection ID (thread ID): 10 Feb 2 17:38:18 tx mysqld: Status: NOT_KILLED Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 17:38:18 tx mysqld: Feb 2 17:38:18 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 17:38:18 tx mysqld: information that should help you find out what is causing the crash. Feb 2 17:38:18 tx mysqld_safe: Number of processes running now: 0 Feb 2 17:38:18 tx mysqld_safe: mysqld restarted Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: The InnoDB memory heap is disabled Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Using Linux native AIO Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Completed initialization of buffer pool Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: highest supported file format is Barracuda. Feb 2 17:38:18 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 84618386241 Feb 2 17:38:18 tx mysqld: 150202 17:38:18 InnoDB: Database was not shut down normally! Feb 2 17:38:18 tx mysqld: InnoDB: Starting crash recovery. Feb 2 17:38:18 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 17:38:18 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 17:38:18 tx mysqld: InnoDB: buffer... Feb 2 17:38:22 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 84618397419 Feb 2 17:38:35 tx mysqld: 150202 17:38:35 InnoDB: Starting an apply batch of log records to the database... Feb 2 17:38:36 tx mysqld: InnoDB: Progress in percents: 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 17:38:36 tx mysqld: InnoDB: Apply batch completed Feb 2 17:38:36 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 17:38:37 tx mysqld: 150202 17:38:37 InnoDB: Waiting for the background threads to start Feb 2 17:38:38 tx mysqld: 150202 17:38:38 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84618397419 Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [ERROR] Function 'ARCHIVE' already exists Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [ERROR] Function 'FEDERATED' already exists Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [ERROR] Function 'BLACKHOLE' already exists Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Note] Event Scheduler: Loaded 0 events Feb 2 17:38:38 tx mysqld: 150202 17:38:38 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 17:38:38 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 17:38:42 tx mysqld: 150202 17:38:42 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 17:38:42 tx mysqld: Feb 2 17:38:42 tx mysqld: 150202 17:38:42 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 17:38:42 tx mysqld: 150202 17:38:42 InnoDB: Starting shutdown... Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: Shutdown completed; log sequence number 84618397419 Feb 2 17:38:43 tx mysqld: 150202 17:38:43 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 17:38:43 tx mysqld: Feb 2 17:38:43 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 17:38:43 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: The InnoDB memory heap is disabled Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: Using Linux native AIO Feb 2 17:38:43 tx mysqld: 150202 17:38:43 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 17:38:44 tx mysqld: 150202 17:38:44 InnoDB: Completed initialization of buffer pool Feb 2 17:38:44 tx mysqld: 150202 17:38:44 InnoDB: highest supported file format is Barracuda. Feb 2 17:38:53 tx mysqld: 150202 17:38:53 InnoDB: Waiting for the background threads to start Feb 2 17:38:54 tx mysqld: 150202 17:38:54 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84618397419 Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [ERROR] Function 'ARCHIVE' already exists Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [ERROR] Function 'FEDERATED' already exists Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [ERROR] Function 'BLACKHOLE' already exists Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Note] Event Scheduler: Loaded 0 events Feb 2 17:38:54 tx mysqld: 150202 17:38:54 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 17:38:54 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 17:38:55 tx /etc/mysql/debian-start[12144]: Upgrading MySQL tables if necessary. Feb 2 17:38:55 tx /etc/mysql/debian-start[12149]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 17:38:55 tx /etc/mysql/debian-start[12149]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 17:38:55 tx /etc/mysql/debian-start[12149]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 17:38:55 tx /etc/mysql/debian-start[12149]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 17:38:55 tx /etc/mysql/debian-start[12160]: Checking for insecure root accounts. Feb 2 17:38:55 tx /etc/mysql/debian-start[12165]: Triggering myisam-recover for all MyISAM tables Feb 2 17:42:06 tx mysqld: 150202 17:42:06 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 17:42:06 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:42:06 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:42:06 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:42:06 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:42:06 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:42:06 tx mysqld: doesn't support. Feb 2 17:42:06 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:42:06 tx mysqld: how you can resolve the problem. Feb 2 17:42:06 tx mysqld: Feb 2 17:42:06 tx mysqld: 150202 17:42:06 [ERROR] Cannot find or open table atest_sn5/dashboardd from Feb 2 17:42:06 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:42:06 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:42:06 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:42:06 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:42:06 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:42:06 tx mysqld: doesn't support. Feb 2 17:42:06 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:42:06 tx mysqld: how you can resolve the problem. Feb 2 17:42:06 tx mysqld: Feb 2 17:42:42 tx mysqld: 150202 17:42:42 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 17:42:42 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 17:42:42 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 17:42:42 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 17:42:42 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 17:42:42 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 17:42:42 tx mysqld: doesn't support. Feb 2 17:42:42 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 17:42:42 tx mysqld: how you can resolve the problem. Feb 2 17:42:42 tx mysqld: Feb 2 20:42:27 tx mysqld: 150202 20:42:27 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 20:42:27 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 20:42:27 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 20:42:27 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 20:42:27 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 20:42:27 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 20:42:27 tx mysqld: doesn't support. Feb 2 20:42:27 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:42:27 tx mysqld: how you can resolve the problem. Feb 2 20:42:27 tx mysqld: Feb 2 20:43:03 tx mysqld: 150202 20:43:03 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 20:43:03 tx mysqld: Feb 2 20:43:03 tx mysqld: 150202 20:43:03 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 20:43:03 tx mysqld: 150202 20:43:03 InnoDB: Starting shutdown... Feb 2 20:43:04 tx mysqld: 150202 20:43:04 InnoDB: Shutdown completed; log sequence number 84618397449 Feb 2 20:43:04 tx mysqld: 150202 20:43:04 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 20:43:04 tx mysqld: Feb 2 20:43:04 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 20:43:05 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: The InnoDB memory heap is disabled Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: Using Linux native AIO Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: Completed initialization of buffer pool Feb 2 20:43:05 tx mysqld: 150202 20:43:05 InnoDB: highest supported file format is Barracuda. Feb 2 20:43:06 tx mysqld: 150202 20:43:06 InnoDB: Waiting for the background threads to start Feb 2 20:43:07 tx mysqld: 150202 20:43:07 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84618397449 Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [ERROR] Function 'ARCHIVE' already exists Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [ERROR] Function 'FEDERATED' already exists Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [ERROR] Function 'BLACKHOLE' already exists Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Note] Event Scheduler: Loaded 0 events Feb 2 20:43:07 tx mysqld: 150202 20:43:07 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 20:43:07 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 20:43:08 tx /etc/mysql/debian-start[16978]: Upgrading MySQL tables if necessary. Feb 2 20:43:08 tx /etc/mysql/debian-start[16981]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 20:43:08 tx /etc/mysql/debian-start[16981]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 20:43:08 tx /etc/mysql/debian-start[16981]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 20:43:08 tx /etc/mysql/debian-start[16981]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 20:43:08 tx /etc/mysql/debian-start[16992]: Checking for insecure root accounts. Feb 2 20:43:08 tx /etc/mysql/debian-start[16997]: Triggering myisam-recover for all MyISAM tables Feb 2 20:43:11 tx mysqld: 150202 20:43:11 [ERROR] mysqld got signal 11 ; Feb 2 20:43:11 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 20:43:11 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 20:43:11 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 20:43:11 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 20:43:11 tx mysqld: something is definitely wrong and this may fail. Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 20:43:11 tx mysqld: key_buffer_size=134217728 Feb 2 20:43:11 tx mysqld: read_buffer_size=2097152 Feb 2 20:43:11 tx mysqld: max_used_connections=2 Feb 2 20:43:11 tx mysqld: max_threads=102 Feb 2 20:43:11 tx mysqld: thread_count=2 Feb 2 20:43:11 tx mysqld: It is possible that mysqld could use up to Feb 2 20:43:11 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 20:43:11 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: Thread pointer: 0x0x7fb0f4bad000 Feb 2 20:43:11 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 20:43:11 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 20:43:11 tx mysqld: terribly wrong... Feb 2 20:43:11 tx mysqld: stack_bottom = 0x7fb125f03e40 thread_stack 0x48000 Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fb1268b470e] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7fb1264a62d7] Feb 2 20:43:11 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fb125555340] Feb 2 20:43:11 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7fb12467dda6] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7fb1267fbecd] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7fb1267622a1] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7fb126767c25] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7fb1266d5258] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7fb1266b488f] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7fb1264ad027] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7fb1264ada3c] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7fb12641089f] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7fb1263dbc72] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7fb1263dc87f] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7fb126365656] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7fb126365cea] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7fb126367ebd] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7fb126425663] Feb 2 20:43:11 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7fb12642575a] Feb 2 20:43:11 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fb12554d182] Feb 2 20:43:11 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb12463800d] Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: Trying to get some variables. Feb 2 20:43:11 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 20:43:11 tx mysqld: Query (0x7fb0f1021018): is an invalid pointer Feb 2 20:43:11 tx mysqld: Connection ID (thread ID): 6 Feb 2 20:43:11 tx mysqld: Status: NOT_KILLED Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 20:43:11 tx mysqld: Feb 2 20:43:11 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 20:43:11 tx mysqld: information that should help you find out what is causing the crash. Feb 2 20:43:11 tx mysqld_safe: Number of processes running now: 0 Feb 2 20:43:11 tx mysqld_safe: mysqld restarted Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: The InnoDB memory heap is disabled Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Using Linux native AIO Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Completed initialization of buffer pool Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: highest supported file format is Barracuda. Feb 2 20:43:11 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 84618397449 Feb 2 20:43:11 tx mysqld: 150202 20:43:11 InnoDB: Database was not shut down normally! Feb 2 20:43:11 tx mysqld: InnoDB: Starting crash recovery. Feb 2 20:43:11 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 20:43:11 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 20:43:11 tx mysqld: InnoDB: buffer... Feb 2 20:43:14 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 84618408501 Feb 2 20:43:15 tx mysqld: 150202 20:43:15 InnoDB: Starting an apply batch of log records to the database... Feb 2 20:43:15 tx mysqld: InnoDB: Progress in percents: 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 20:43:15 tx mysqld: InnoDB: Apply batch completed Feb 2 20:43:15 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 20:43:16 tx mysqld: 150202 20:43:16 InnoDB: Waiting for the background threads to start Feb 2 20:43:17 tx mysqld: 150202 20:43:17 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 84618408501 Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [ERROR] Function 'ARCHIVE' already exists Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [ERROR] Function 'FEDERATED' already exists Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [ERROR] Function 'BLACKHOLE' already exists Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Note] Event Scheduler: Loaded 0 events Feb 2 20:43:17 tx mysqld: 150202 20:43:17 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 20:43:17 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 20:43:21 tx mysqld: 150202 20:43:21 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 20:43:21 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 20:43:21 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 20:43:21 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 20:43:21 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 20:43:21 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 20:43:21 tx mysqld: doesn't support. Feb 2 20:43:21 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:43:21 tx mysqld: how you can resolve the problem. Feb 2 20:43:21 tx mysqld: Feb 2 20:44:40 tx mysqld: 150202 20:44:40 InnoDB: Error: table `atest_sn5`.`orders_products` does not exist in the InnoDB internal Feb 2 20:44:40 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 20:44:40 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 20:44:40 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 20:44:40 tx mysqld: InnoDB: You can look for further help from Feb 2 20:44:40 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:44:41 tx mysqld: 150202 20:44:41 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 20:44:41 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 20:44:41 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 20:44:41 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 20:44:41 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 20:44:41 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 20:44:41 tx mysqld: doesn't support. Feb 2 20:44:41 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:44:41 tx mysqld: how you can resolve the problem. Feb 2 20:44:41 tx mysqld: Feb 2 20:44:41 tx mysqld: 150202 20:44:41 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 20:44:41 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 20:44:41 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 20:44:41 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 20:44:41 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 20:44:41 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 20:44:41 tx mysqld: doesn't support. Feb 2 20:44:41 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:44:41 tx mysqld: how you can resolve the problem. Feb 2 20:44:41 tx mysqld: Feb 2 20:44:46 tx mysqld: 150202 20:44:46 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 20:44:46 tx mysqld: 150202 20:44:46 InnoDB: Operating system error number 17 in a file operation. Feb 2 20:44:46 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 20:44:46 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 20:44:46 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 20:44:46 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 20:44:46 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 20:44:46 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 20:44:46 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 20:44:46 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 20:44:46 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 20:44:46 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 20:45:28 tx mysqld: 150202 20:45:28 [ERROR] Cannot find or open table atest_sn5/dashboard from Feb 2 20:45:28 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 20:45:28 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 20:45:28 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 20:45:28 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 20:45:28 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 20:45:28 tx mysqld: doesn't support. Feb 2 20:45:28 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:45:28 tx mysqld: how you can resolve the problem. Feb 2 20:45:28 tx mysqld: Feb 2 20:46:15 tx mysqld: 150202 20:46:15 InnoDB: Error: table `atest_sn5`.`dashboard` does not exist in the InnoDB internal Feb 2 20:46:15 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 20:46:15 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 20:46:15 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 20:46:15 tx mysqld: InnoDB: You can look for further help from Feb 2 20:46:15 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 20:53:21 tx mysqld: 150202 20:53:21 [Warning] Aborted connection 2 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 21:17:28 tx mysqld: 150202 21:17:28 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 21:17:28 tx mysqld: Feb 2 21:17:28 tx mysqld: 150202 21:17:28 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 21:17:28 tx mysqld: 150202 21:17:28 InnoDB: Starting shutdown... Feb 2 21:17:28 tx mysqld: 150202 21:17:28 InnoDB: Waiting for 14 pages to be flushed Feb 2 21:17:29 tx mysqld: 150202 21:17:29 InnoDB: Shutdown completed; log sequence number 86367569122 Feb 2 21:17:29 tx mysqld: 150202 21:17:29 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 21:17:29 tx mysqld: Feb 2 21:17:29 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 21:17:37 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: The InnoDB memory heap is disabled Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: Using Linux native AIO Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: Completed initialization of buffer pool Feb 2 21:17:37 tx mysqld: 150202 21:17:37 InnoDB: highest supported file format is Barracuda. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/addressess.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/addressess_attributes.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/advertisements.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/advertisements_cities.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/announcements.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/banks.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/cities.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/cities_alternatives.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/countries.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/ethnicgroups.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/ethnicgroups_nationalities.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/eventscalendar.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/hairs.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/intimates.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/languages.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/nationalities.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/news.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers_booked.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers_prices.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/old_payments.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/orders.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/pages.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/pictures.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/products.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/products_booked.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_bookings.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_languages.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_notes.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_personals.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_phones.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_phones_blacklist.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_services.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/regions.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/replacements.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/satelites.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/servicegroups.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/servicegroups_services.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/services.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/tasks.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/translationfronts.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/translations.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_address_access.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_address_cash.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_permissions.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:17:38 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:17:38 tx mysqld: InnoDB: If you are installing InnoDB, remember that you must create Feb 2 21:17:38 tx mysqld: InnoDB: directories yourself, InnoDB does not create them. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Error: trying to open a table, but could not Feb 2 21:17:38 tx mysqld: InnoDB: open the tablespace file './atest_sn5/videos.ibd'! Feb 2 21:17:38 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:17:38 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:17:38 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:17:38 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:17:38 tx mysqld: InnoDB: Please refer to Feb 2 21:17:38 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:17:38 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:17:38 tx mysqld: 150202 21:17:38 InnoDB: Waiting for the background threads to start Feb 2 21:17:39 tx mysqld: 150202 21:17:39 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 86367569122 Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [ERROR] Function 'ARCHIVE' already exists Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [ERROR] Function 'FEDERATED' already exists Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [ERROR] Function 'BLACKHOLE' already exists Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Note] Event Scheduler: Loaded 0 events Feb 2 21:17:39 tx mysqld: 150202 21:17:39 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 21:17:39 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 21:17:40 tx /etc/mysql/debian-start[19299]: Upgrading MySQL tables if necessary. Feb 2 21:17:40 tx /etc/mysql/debian-start[19302]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 21:17:40 tx /etc/mysql/debian-start[19302]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 21:17:40 tx /etc/mysql/debian-start[19302]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 21:17:40 tx /etc/mysql/debian-start[19302]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 21:17:40 tx /etc/mysql/debian-start[19313]: Checking for insecure root accounts. Feb 2 21:17:40 tx /etc/mysql/debian-start[19319]: Triggering myisam-recover for all MyISAM tables Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/addressess', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11820 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/addressess.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/addressess_attributes', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11822 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/addressess_attributes.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/old_payments', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11835 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/old_payments.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/newspapers_booked', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11830 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers_booked.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_bookings', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11846 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_bookings.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/users_address_access', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11853 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_address_access.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/users_address_cash', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11854 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_address_cash.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/addressess' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11820, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`addressess`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/addressess_attributes' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11822, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`addressess_attributes`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/advertisements', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11667 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/advertisements.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/advertisements_cities', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11696 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/advertisements_cities.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/advertisements' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11667, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`advertisements`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/advertisements_cities' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11696, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`advertisements_cities`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/announcements', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11824 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/announcements.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/announcements' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11824, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`announcements`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/banks', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11599 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/banks.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/banks' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11599, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`banks`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/cities', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11727 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/cities.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/cities_alternatives', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11734 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/cities_alternatives.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/cities' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11727, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`cities`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/cities_alternatives' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11734, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`cities_alternatives`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/countries', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11723 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/countries.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/regions', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11725 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/regions.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/countries' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11723, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`countries`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/ethnicgroups', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11697 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/ethnicgroups.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/ethnicgroups_nationalities', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11732 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/ethnicgroups_nationalities.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/ethnicgroups' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11697, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`ethnicgroups`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/ethnicgroups_nationalities' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11732, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`ethnicgroups_nationalities`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/eventscalendar', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11606 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/eventscalendar.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/eventscalendar' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11606, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`eventscalendar`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/hairs', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11711 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/hairs.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11844 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/news', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11826 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/news.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/orders', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11839 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/orders.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/products_booked', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11631 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/products_booked.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_notes', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11635 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_notes.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_personals', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11848 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_personals.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_phones', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11637 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_phones.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/pictures', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11841 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/pictures.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/videos', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11857 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/videos.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/hairs' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11711, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`hairs`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/intimates', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11715 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/intimates.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/intimates' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11715, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`intimates`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/languages', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11698 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/languages.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/languages' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11698, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`languages`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/nationalities', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11706 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/nationalities.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/nationalities' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11706, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`nationalities`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/news' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11826, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`news`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/newspapers', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11828 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/newspapers_prices', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11832 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/newspapers_prices.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/newspapers' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11828, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`newspapers`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/newspapers_booked' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11830, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`newspapers_booked`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/newspapers_prices' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11832, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`newspapers_prices`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/old_payments' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11835, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`old_payments`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/orders' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11839, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`orders`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/pages', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11627 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/pages.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/pages' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11627, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`pages`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/pictures' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11841, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`pictures`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/products', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11630 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/products.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/products' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11630, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`products`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/products_booked' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11631, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`products_booked`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11844, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_bookings' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11846, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_bookings`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_languages', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11634 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_languages.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_languages' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11634, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_languages`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_notes' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11635, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_notes`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_personals' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11848, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_personals`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_phones' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11637, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_phones`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_phones_blacklist', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11736 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_phones_blacklist.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_phones_blacklist' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11736, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_phones_blacklist`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/profiles_services', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11638 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/profiles_services.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/profiles_services' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11638, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`profiles_services`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/regions' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11725, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`regions`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/replacements', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11641 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/replacements.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/replacements' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11641, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`replacements`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/satelites', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11642 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/satelites.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/satelites' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11642, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`satelites`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/servicegroups', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11702 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/servicegroups.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/servicegroups_services', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11703 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/servicegroups_services.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/servicegroups' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11702, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`servicegroups`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/servicegroups_services' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11703, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`servicegroups_services`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/services', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11647 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/services.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/services' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11647, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`services`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/tasks', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11851 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/tasks.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/tasks' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11851, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`tasks`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/translationfronts', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11650 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/translationfronts.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/translationfronts' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11650, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`translationfronts`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/translations', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11651 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/translations.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/translations' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11651, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`translations`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/users', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11852 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: error: space object of table 'atest_sn5/users_permissions', Feb 2 21:20:19 tx mysqld: InnoDB: space id 11855 did not exist in memory. Retrying an open. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Operating system error number 2 in a file operation. Feb 2 21:20:19 tx mysqld: InnoDB: The error means the system cannot find the path specified. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: trying to open a table, but could not Feb 2 21:20:19 tx mysqld: InnoDB: open the tablespace file './atest_sn5/users_permissions.ibd'! Feb 2 21:20:19 tx mysqld: InnoDB: Have you moved InnoDB .ibd files around without using the Feb 2 21:20:19 tx mysqld: InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? Feb 2 21:20:19 tx mysqld: InnoDB: It is also possible that this is a temporary table #sql..., Feb 2 21:20:19 tx mysqld: InnoDB: and MySQL removed the .ibd file for this. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/users' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11852, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`users`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/users_address_access' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11853, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`users_address_access`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/users_address_cash' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11854, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`users_address_cash`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/users_permissions' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11855, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`users_permissions`. Feb 2 21:20:19 tx mysqld: 150202 21:20:19 InnoDB: Error: table 'atest_sn5/videos' Feb 2 21:20:19 tx mysqld: InnoDB: in InnoDB data dictionary has tablespace id 11857, Feb 2 21:20:19 tx mysqld: InnoDB: but tablespace with that id or name does not exist. Have Feb 2 21:20:19 tx mysqld: InnoDB: you deleted or moved .ibd files? Feb 2 21:20:19 tx mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE Feb 2 21:20:19 tx mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the Feb 2 21:20:19 tx mysqld: InnoDB: table still exists in the InnoDB internal data dictionary. Feb 2 21:20:19 tx mysqld: InnoDB: Please refer to Feb 2 21:20:19 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html Feb 2 21:20:19 tx mysqld: InnoDB: for how to resolve the issue. Feb 2 21:20:19 tx mysqld: InnoDB: We removed now the InnoDB internal data dictionary entry Feb 2 21:20:19 tx mysqld: InnoDB: of table `atest_sn5`.`videos`. Feb 2 22:08:13 tx mysqld: 150202 22:08:13 InnoDB: Error: in ALTER TABLE `atest_sn5`.`old_newspapers_booked` Feb 2 22:08:13 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 22:08:13 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 22:08:13 tx mysqld: 150202 22:08:13 InnoDB: Error: in ALTER TABLE `atest_sn5`.`old_products_booked` Feb 2 22:08:13 tx mysqld: InnoDB: has or is referenced in foreign key constraints Feb 2 22:08:13 tx mysqld: InnoDB: which are not compatible with the new table definition. Feb 2 22:14:13 tx mysqld: 150202 22:14:13 [ERROR] mysqld got signal 11 ; Feb 2 22:14:13 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 22:14:13 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 22:14:13 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 22:14:13 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 22:14:13 tx mysqld: something is definitely wrong and this may fail. Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 22:14:13 tx mysqld: key_buffer_size=134217728 Feb 2 22:14:13 tx mysqld: read_buffer_size=2097152 Feb 2 22:14:13 tx mysqld: max_used_connections=2 Feb 2 22:14:13 tx mysqld: max_threads=102 Feb 2 22:14:13 tx mysqld: thread_count=2 Feb 2 22:14:13 tx mysqld: It is possible that mysqld could use up to Feb 2 22:14:13 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 22:14:13 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: Thread pointer: 0x0x7fcdc5bad000 Feb 2 22:14:13 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 22:14:13 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 22:14:13 tx mysqld: terribly wrong... Feb 2 22:14:13 tx mysqld: stack_bottom = 0x7fcdf6e7fe40 thread_stack 0x48000 Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fcdf77e770e] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7fcdf73d92d7] Feb 2 22:14:13 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fcdf6488340] Feb 2 22:14:13 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7fcdf55b0da6] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7fcdf772eecd] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7fcdf76952a1] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7fcdf769ac25] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7fcdf7608258] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7fcdf75e788f] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7fcdf73e0027] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7fcdf73e0a3c] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7fcdf734389f] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7fcdf730ec72] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7fcdf730f87f] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7fcdf7298656] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7fcdf7298cea] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7fcdf729aebd] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7fcdf7358663] Feb 2 22:14:13 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7fcdf735875a] Feb 2 22:14:13 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fcdf6480182] Feb 2 22:14:13 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fcdf556b00d] Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: Trying to get some variables. Feb 2 22:14:13 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 22:14:13 tx mysqld: Query (0x7fcdc101d018): is an invalid pointer Feb 2 22:14:13 tx mysqld: Connection ID (thread ID): 182 Feb 2 22:14:13 tx mysqld: Status: NOT_KILLED Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 22:14:13 tx mysqld: Feb 2 22:14:13 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 22:14:13 tx mysqld: information that should help you find out what is causing the crash. Feb 2 22:14:13 tx mysqld_safe: Number of processes running now: 0 Feb 2 22:14:13 tx mysqld_safe: mysqld restarted Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: The InnoDB memory heap is disabled Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Using Linux native AIO Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Completed initialization of buffer pool Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: highest supported file format is Barracuda. Feb 2 22:14:13 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 89427611256 Feb 2 22:14:13 tx mysqld: 150202 22:14:13 InnoDB: Database was not shut down normally! Feb 2 22:14:13 tx mysqld: InnoDB: Starting crash recovery. Feb 2 22:14:13 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 22:14:15 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 22:14:15 tx mysqld: InnoDB: buffer... Feb 2 22:14:16 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 89427731601 Feb 2 22:14:16 tx mysqld: 150202 22:14:16 InnoDB: Starting an apply batch of log records to the database... Feb 2 22:14:17 tx mysqld: InnoDB: Progress in percents: 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 22:14:17 tx mysqld: InnoDB: Apply batch completed Feb 2 22:14:17 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 22:14:17 tx mysqld: 150202 22:14:17 InnoDB: Waiting for the background threads to start Feb 2 22:14:18 tx mysqld: 150202 22:14:18 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427731601 Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [ERROR] Function 'FEDERATED' already exists Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Note] Event Scheduler: Loaded 0 events Feb 2 22:14:18 tx mysqld: 150202 22:14:18 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:14:18 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:14:55 tx mysqld: 150202 22:14:55 [ERROR] mysqld: Table './mysql/proc' is marked as crashed and should be repaired Feb 2 22:14:55 tx mysqld: 150202 22:14:55 [ERROR] mysqld: Table 'proc' is marked as crashed and should be repaired Feb 2 22:14:55 tx mysqld: 150202 22:14:55 [Warning] Checking table: './mysql/proc' Feb 2 22:14:57 tx mysqld: 150202 22:14:57 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:14:57 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:14:57 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:14:57 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:14:57 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:14:57 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:14:57 tx mysqld: doesn't support. Feb 2 22:14:57 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:14:57 tx mysqld: how you can resolve the problem. Feb 2 22:14:57 tx mysqld: Feb 2 22:14:57 tx mysqld: 150202 22:14:57 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:14:57 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:14:57 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:14:57 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:14:57 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:14:57 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:14:57 tx mysqld: doesn't support. Feb 2 22:14:57 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:14:57 tx mysqld: how you can resolve the problem. Feb 2 22:14:57 tx mysqld: Feb 2 22:15:08 tx mysqld: 150202 22:15:08 InnoDB: Error: table `atest_sn5`.`orders_products` does not exist in the InnoDB internal Feb 2 22:15:08 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 22:15:08 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 22:15:08 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 22:15:08 tx mysqld: InnoDB: You can look for further help from Feb 2 22:15:08 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:16:00 tx mysqld: 150202 22:16:00 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 22:16:00 tx mysqld: 150202 22:16:00 InnoDB: Operating system error number 17 in a file operation. Feb 2 22:16:00 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 22:16:00 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 22:16:00 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 22:16:00 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 22:16:00 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 22:16:00 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 22:16:00 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 22:16:00 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 22:16:00 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 22:16:00 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 22:16:05 tx mysqld: 150202 22:16:05 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 22:16:05 tx mysqld: 150202 22:16:05 InnoDB: Operating system error number 17 in a file operation. Feb 2 22:16:05 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 22:16:05 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 22:16:05 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 22:16:05 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 22:16:05 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 22:16:05 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 22:16:05 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 22:16:05 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 22:16:05 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 22:16:05 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 22:16:26 tx mysqld: 150202 22:16:26 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 22:16:26 tx mysqld: 150202 22:16:26 InnoDB: Operating system error number 17 in a file operation. Feb 2 22:16:26 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 22:16:26 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 22:16:26 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 22:16:26 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 22:16:26 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 22:16:26 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 22:16:26 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 22:16:26 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 22:16:26 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 22:16:26 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 22:17:10 tx mysqld: 150202 22:17:10 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 22:17:10 tx mysqld: 150202 22:17:10 InnoDB: Operating system error number 17 in a file operation. Feb 2 22:17:10 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 22:17:10 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 22:17:10 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 22:17:10 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 22:17:10 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 22:17:10 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 22:17:10 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 22:17:10 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 22:17:10 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 22:17:10 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: Warning: trying to init to the tablespace memory cache Feb 2 22:17:54 tx mysqld: InnoDB: a tablespace 12291 of name './atest_sn5/orders_products.ibd', Feb 2 22:17:54 tx mysqld: InnoDB: but a tablespace 12278 of the same name Feb 2 22:17:54 tx mysqld: InnoDB: already exists in the tablespace memory cache! Feb 2 22:17:54 tx mysqld: InnoDB: We assume that InnoDB did a crash recovery, and you had Feb 2 22:17:54 tx mysqld: InnoDB: an .ibd file for which the table did not exist in the Feb 2 22:17:54 tx mysqld: InnoDB: InnoDB internal data dictionary in the ibdata files. Feb 2 22:17:54 tx mysqld: InnoDB: We assume that you later removed the .ibd and .frm files, Feb 2 22:17:54 tx mysqld: InnoDB: and are now trying to recreate the table. We now remove the Feb 2 22:17:54 tx mysqld: InnoDB: conflicting tablespace object from the memory cache and try Feb 2 22:17:54 tx mysqld: InnoDB: the init again. Feb 2 22:17:54 tx mysqld: 150202 22:17:54 [ERROR] mysqld got signal 11 ; Feb 2 22:17:54 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 22:17:54 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 22:17:54 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 22:17:54 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 22:17:54 tx mysqld: something is definitely wrong and this may fail. Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 22:17:54 tx mysqld: key_buffer_size=134217728 Feb 2 22:17:54 tx mysqld: read_buffer_size=2097152 Feb 2 22:17:54 tx mysqld: max_used_connections=3 Feb 2 22:17:54 tx mysqld: max_threads=102 Feb 2 22:17:54 tx mysqld: thread_count=1 Feb 2 22:17:54 tx mysqld: It is possible that mysqld could use up to Feb 2 22:17:54 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 22:17:54 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: Thread pointer: 0x0x7fbe6a76d000 Feb 2 22:17:54 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 22:17:54 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 22:17:54 tx mysqld: terribly wrong... Feb 2 22:17:54 tx mysqld: stack_bottom = 0x7fbe9b8c4e40 thread_stack 0x48000 Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fbe9c22c70e] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7fbe9be1e2d7] Feb 2 22:17:54 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fbe9aecd340] Feb 2 22:17:54 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7fbe99ff5da6] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7fbe9c173ecd] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7fbe9c0da2a1] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7fbe9c0dfc25] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7fbe9c04d258] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7fbe9c02c88f] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7fbe9be25027] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7fbe9be25a3c] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7fbe9bd8889f] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7fbe9bd53c72] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7fbe9bd5487f] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7fbe9bcdd656] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7fbe9bcddcea] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7fbe9bcdfebd] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7fbe9bd9d663] Feb 2 22:17:54 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7fbe9bd9d75a] Feb 2 22:17:54 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fbe9aec5182] Feb 2 22:17:54 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbe99fb000d] Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: Trying to get some variables. Feb 2 22:17:54 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 22:17:54 tx mysqld: Query (0x7fbe65021018): is an invalid pointer Feb 2 22:17:54 tx mysqld: Connection ID (thread ID): 2 Feb 2 22:17:54 tx mysqld: Status: NOT_KILLED Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 22:17:54 tx mysqld: Feb 2 22:17:54 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 22:17:54 tx mysqld: information that should help you find out what is causing the crash. Feb 2 22:17:54 tx mysqld_safe: Number of processes running now: 0 Feb 2 22:17:54 tx mysqld_safe: mysqld restarted Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: The InnoDB memory heap is disabled Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: Using Linux native AIO Feb 2 22:17:54 tx mysqld: 150202 22:17:54 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:17:55 tx mysqld: 150202 22:17:55 InnoDB: Completed initialization of buffer pool Feb 2 22:17:55 tx mysqld: 150202 22:17:55 InnoDB: highest supported file format is Barracuda. Feb 2 22:17:55 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 89427866988 Feb 2 22:17:55 tx mysqld: 150202 22:17:55 InnoDB: Database was not shut down normally! Feb 2 22:17:55 tx mysqld: InnoDB: Starting crash recovery. Feb 2 22:17:55 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 22:17:55 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 22:17:55 tx mysqld: InnoDB: buffer... Feb 2 22:17:55 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 89427874872 Feb 2 22:18:00 tx mysqld: 150202 22:18:00 InnoDB: Starting an apply batch of log records to the database... Feb 2 22:18:00 tx mysqld: InnoDB: Progress in percents: 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 22:18:00 tx mysqld: InnoDB: Apply batch completed Feb 2 22:18:00 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 22:18:00 tx mysqld: 150202 22:18:00 InnoDB: Waiting for the background threads to start Feb 2 22:18:01 tx mysqld: 150202 22:18:01 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427874872 Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [ERROR] Function 'FEDERATED' already exists Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Note] Event Scheduler: Loaded 0 events Feb 2 22:18:01 tx mysqld: 150202 22:18:01 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:18:01 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:18:08 tx mysqld: 150202 22:18:08 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 22:18:08 tx mysqld: Feb 2 22:18:08 tx mysqld: 150202 22:18:08 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 22:18:08 tx mysqld: 150202 22:18:08 InnoDB: Starting shutdown... Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Shutdown completed; log sequence number 89427874872 Feb 2 22:18:09 tx mysqld: 150202 22:18:09 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 22:18:09 tx mysqld: Feb 2 22:18:09 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 22:18:09 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: The InnoDB memory heap is disabled Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Using Linux native AIO Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: Completed initialization of buffer pool Feb 2 22:18:09 tx mysqld: 150202 22:18:09 InnoDB: highest supported file format is Barracuda. Feb 2 22:18:11 tx mysqld: 150202 22:18:11 InnoDB: Waiting for the background threads to start Feb 2 22:18:12 tx mysqld: 150202 22:18:12 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427874872 Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [ERROR] Function 'FEDERATED' already exists Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Note] Event Scheduler: Loaded 0 events Feb 2 22:18:12 tx mysqld: 150202 22:18:12 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:18:12 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:18:13 tx /etc/mysql/debian-start[24674]: Upgrading MySQL tables if necessary. Feb 2 22:18:13 tx /etc/mysql/debian-start[24677]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 22:18:13 tx /etc/mysql/debian-start[24677]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 22:18:13 tx /etc/mysql/debian-start[24677]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 22:18:13 tx /etc/mysql/debian-start[24677]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 22:18:13 tx /etc/mysql/debian-start[24688]: Checking for insecure root accounts. Feb 2 22:18:13 tx /etc/mysql/debian-start[24693]: Triggering myisam-recover for all MyISAM tables Feb 2 22:18:16 tx mysqld: 150202 22:18:16 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:18:16 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:18:16 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:18:16 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:18:16 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:18:16 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:18:16 tx mysqld: doesn't support. Feb 2 22:18:16 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:18:16 tx mysqld: how you can resolve the problem. Feb 2 22:18:16 tx mysqld: Feb 2 22:18:18 tx mysqld: 150202 22:18:18 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:18:18 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:18:18 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:18:18 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:18:18 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:18:18 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:18:18 tx mysqld: doesn't support. Feb 2 22:18:18 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:18:18 tx mysqld: how you can resolve the problem. Feb 2 22:18:18 tx mysqld: Feb 2 22:18:40 tx mysqld: 150202 22:18:40 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:18:40 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:18:40 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:18:40 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:18:40 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:18:40 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:18:40 tx mysqld: doesn't support. Feb 2 22:18:40 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:18:40 tx mysqld: how you can resolve the problem. Feb 2 22:18:40 tx mysqld: Feb 2 22:20:33 tx mysqld: 150202 22:20:33 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:20:33 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:20:33 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:20:33 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:20:33 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:20:33 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:20:33 tx mysqld: doesn't support. Feb 2 22:20:33 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:20:33 tx mysqld: how you can resolve the problem. Feb 2 22:20:33 tx mysqld: Feb 2 22:20:33 tx mysqld: 150202 22:20:33 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:20:33 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:20:33 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:20:33 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:20:33 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:20:33 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:20:33 tx mysqld: doesn't support. Feb 2 22:20:33 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:20:33 tx mysqld: how you can resolve the problem. Feb 2 22:20:33 tx mysqld: Feb 2 22:21:22 tx mysqld: 150202 22:21:22 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 22:21:22 tx mysqld: Feb 2 22:21:22 tx mysqld: 150202 22:21:22 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 22:21:22 tx mysqld: 150202 22:21:22 InnoDB: Starting shutdown... Feb 2 22:21:23 tx mysqld: 150202 22:21:23 InnoDB: Shutdown completed; log sequence number 89427874882 Feb 2 22:21:23 tx mysqld: 150202 22:21:23 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 22:21:23 tx mysqld: Feb 2 22:21:23 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 22:21:40 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: The InnoDB memory heap is disabled Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Using Linux native AIO Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Completed initialization of buffer pool Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: highest supported file format is Barracuda. Feb 2 22:21:40 tx mysqld: 150202 22:21:40 InnoDB: Waiting for the background threads to start Feb 2 22:21:41 tx mysqld: 150202 22:21:41 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427874882 Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [ERROR] Function 'FEDERATED' already exists Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Note] Event Scheduler: Loaded 0 events Feb 2 22:21:41 tx mysqld: 150202 22:21:41 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:21:41 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:21:42 tx /etc/mysql/debian-start[25815]: Upgrading MySQL tables if necessary. Feb 2 22:21:42 tx /etc/mysql/debian-start[25818]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 22:21:42 tx /etc/mysql/debian-start[25818]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 22:21:42 tx /etc/mysql/debian-start[25818]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 22:21:42 tx /etc/mysql/debian-start[25818]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 22:21:42 tx /etc/mysql/debian-start[25829]: Checking for insecure root accounts. Feb 2 22:21:42 tx /etc/mysql/debian-start[25834]: Triggering myisam-recover for all MyISAM tables Feb 2 22:21:52 tx mysqld: 150202 22:21:52 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:21:52 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:21:52 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:21:52 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:21:52 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:21:52 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:21:52 tx mysqld: doesn't support. Feb 2 22:21:52 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:21:52 tx mysqld: how you can resolve the problem. Feb 2 22:21:52 tx mysqld: Feb 2 22:21:52 tx mysqld: 150202 22:21:52 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:21:52 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:21:52 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:21:52 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:21:52 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:21:52 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:21:52 tx mysqld: doesn't support. Feb 2 22:21:52 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:21:52 tx mysqld: how you can resolve the problem. Feb 2 22:21:52 tx mysqld: Feb 2 22:22:02 tx mysqld: 150202 22:22:02 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:02 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:02 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:02 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:02 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:02 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:02 tx mysqld: doesn't support. Feb 2 22:22:02 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:02 tx mysqld: how you can resolve the problem. Feb 2 22:22:02 tx mysqld: Feb 2 22:22:02 tx mysqld: 150202 22:22:02 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:02 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:02 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:02 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:02 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:02 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:02 tx mysqld: doesn't support. Feb 2 22:22:02 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:02 tx mysqld: how you can resolve the problem. Feb 2 22:22:02 tx mysqld: Feb 2 22:22:11 tx mysqld: 150202 22:22:11 [Warning] Access denied for user 'root'@'localhost' (using password: NO) Feb 2 22:22:12 tx mysqld: 150202 22:22:12 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:12 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:12 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:12 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:12 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:12 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:12 tx mysqld: doesn't support. Feb 2 22:22:12 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:12 tx mysqld: how you can resolve the problem. Feb 2 22:22:12 tx mysqld: Feb 2 22:22:17 tx mysqld: 150202 22:22:17 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:17 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:17 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:17 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:17 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:17 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:17 tx mysqld: doesn't support. Feb 2 22:22:17 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:17 tx mysqld: how you can resolve the problem. Feb 2 22:22:17 tx mysqld: Feb 2 22:22:17 tx mysqld: 150202 22:22:17 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:17 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:17 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:17 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:17 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:17 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:17 tx mysqld: doesn't support. Feb 2 22:22:17 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:17 tx mysqld: how you can resolve the problem. Feb 2 22:22:17 tx mysqld: Feb 2 22:22:19 tx mysqld: 150202 22:22:19 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:19 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:19 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:19 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:19 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:19 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:19 tx mysqld: doesn't support. Feb 2 22:22:19 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:19 tx mysqld: how you can resolve the problem. Feb 2 22:22:19 tx mysqld: Feb 2 22:22:20 tx mysqld: 150202 22:22:20 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:20 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:20 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:20 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:20 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:20 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:20 tx mysqld: doesn't support. Feb 2 22:22:20 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:20 tx mysqld: how you can resolve the problem. Feb 2 22:22:20 tx mysqld: Feb 2 22:22:20 tx mysqld: 150202 22:22:20 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:22:20 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:22:20 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:22:20 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:22:20 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:22:20 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:22:20 tx mysqld: doesn't support. Feb 2 22:22:20 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:20 tx mysqld: how you can resolve the problem. Feb 2 22:22:20 tx mysqld: Feb 2 22:22:23 tx mysqld: 150202 22:22:23 InnoDB: Error: table `atest_sn5`.`orders_products` does not exist in the InnoDB internal Feb 2 22:22:23 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 22:22:23 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 22:22:23 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 22:22:23 tx mysqld: InnoDB: You can look for further help from Feb 2 22:22:23 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:22:51 tx mysqld: 150202 22:22:51 [Note] /usr/sbin/mysqld: Normal shutdown Feb 2 22:22:51 tx mysqld: Feb 2 22:22:51 tx mysqld: 150202 22:22:51 [Note] Event Scheduler: Purging the queue. 0 events Feb 2 22:22:51 tx mysqld: 150202 22:22:51 InnoDB: Starting shutdown... Feb 2 22:22:52 tx mysqld: 150202 22:22:52 InnoDB: Shutdown completed; log sequence number 89427874892 Feb 2 22:22:52 tx mysqld: 150202 22:22:52 [Note] /usr/sbin/mysqld: Shutdown complete Feb 2 22:22:52 tx mysqld: Feb 2 22:22:52 tx mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Feb 2 22:23:23 tx mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: The InnoDB memory heap is disabled Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: Using Linux native AIO Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: Completed initialization of buffer pool Feb 2 22:23:24 tx mysqld: 150202 22:23:24 InnoDB: highest supported file format is Barracuda. Feb 2 22:23:25 tx mysqld: 150202 22:23:25 InnoDB: Waiting for the background threads to start Feb 2 22:23:26 tx mysqld: 150202 22:23:26 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427874892 Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [ERROR] Function 'FEDERATED' already exists Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Note] Event Scheduler: Loaded 0 events Feb 2 22:23:26 tx mysqld: 150202 22:23:26 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:23:26 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:23:26 tx /etc/mysql/debian-start[26992]: Upgrading MySQL tables if necessary. Feb 2 22:23:26 tx /etc/mysql/debian-start[26995]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Feb 2 22:23:26 tx /etc/mysql/debian-start[26995]: Looking for 'mysql' as: /usr/bin/mysql Feb 2 22:23:26 tx /etc/mysql/debian-start[26995]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 2 22:23:26 tx /etc/mysql/debian-start[26995]: This installation of MySQL is already upgraded to 5.5.40-MariaDB, use --force if you still need to run mysql_upgrade Feb 2 22:23:26 tx /etc/mysql/debian-start[27006]: Checking for insecure root accounts. Feb 2 22:23:26 tx /etc/mysql/debian-start[27011]: Triggering myisam-recover for all MyISAM tables Feb 2 22:24:17 tx mysqld: 150202 22:24:17 [ERROR] mysqld got signal 11 ; Feb 2 22:24:17 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 22:24:17 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 22:24:17 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 22:24:17 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 22:24:17 tx mysqld: something is definitely wrong and this may fail. Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 22:24:17 tx mysqld: key_buffer_size=134217728 Feb 2 22:24:17 tx mysqld: read_buffer_size=2097152 Feb 2 22:24:17 tx mysqld: max_used_connections=1 Feb 2 22:24:17 tx mysqld: max_threads=102 Feb 2 22:24:17 tx mysqld: thread_count=1 Feb 2 22:24:17 tx mysqld: It is possible that mysqld could use up to Feb 2 22:24:17 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 22:24:17 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: Thread pointer: 0x0x7f00f02f3000 Feb 2 22:24:17 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 22:24:17 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 22:24:17 tx mysqld: terribly wrong... Feb 2 22:24:17 tx mysqld: stack_bottom = 0x7f01216f6e40 thread_stack 0x48000 Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f012205e70e] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f0121c502d7] Feb 2 22:24:17 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f0120cff340] Feb 2 22:24:17 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7f011fe27da6] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7f0121fa5ecd] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7f0121f0c2a1] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7f0121f11c25] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7f0121e7f258] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7f0121e5e88f] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7f0121c57027] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7f0121c57a3c] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7f0121bba89f] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7f0121b85c72] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7f0121b8687f] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7f0121b0f656] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7f0121b0fcea] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7f0121b11ebd] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7f0121bcf663] Feb 2 22:24:17 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7f0121bcf75a] Feb 2 22:24:17 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f0120cf7182] Feb 2 22:24:17 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f011fde200d] Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: Trying to get some variables. Feb 2 22:24:17 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 22:24:17 tx mysqld: Query (0x7f00eb81d018): is an invalid pointer Feb 2 22:24:17 tx mysqld: Connection ID (thread ID): 76 Feb 2 22:24:17 tx mysqld: Status: NOT_KILLED Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 22:24:17 tx mysqld: Feb 2 22:24:17 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 22:24:17 tx mysqld: information that should help you find out what is causing the crash. Feb 2 22:24:17 tx mysqld_safe: Number of processes running now: 0 Feb 2 22:24:17 tx mysqld_safe: mysqld restarted Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: The InnoDB memory heap is disabled Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Using Linux native AIO Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Completed initialization of buffer pool Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: highest supported file format is Barracuda. Feb 2 22:24:17 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 89427874902 Feb 2 22:24:17 tx mysqld: 150202 22:24:17 InnoDB: Database was not shut down normally! Feb 2 22:24:17 tx mysqld: InnoDB: Starting crash recovery. Feb 2 22:24:17 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 22:24:17 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 22:24:17 tx mysqld: InnoDB: buffer... Feb 2 22:24:18 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 89427883436 Feb 2 22:24:18 tx mysqld: 150202 22:24:18 InnoDB: Starting an apply batch of log records to the database... Feb 2 22:24:18 tx mysqld: InnoDB: Progress in percents: 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 22:24:18 tx mysqld: InnoDB: Apply batch completed Feb 2 22:24:18 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 22:24:19 tx mysqld: 150202 22:24:19 InnoDB: Waiting for the background threads to start Feb 2 22:24:20 tx mysqld: 150202 22:24:20 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89427883436 Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [ERROR] Function 'FEDERATED' already exists Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Note] Event Scheduler: Loaded 0 events Feb 2 22:24:20 tx mysqld: 150202 22:24:20 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:24:20 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 2 22:24:22 tx mysqld: 150202 22:24:22 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:24:22 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:24:22 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:24:22 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:24:22 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:24:22 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:24:22 tx mysqld: doesn't support. Feb 2 22:24:22 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:24:22 tx mysqld: how you can resolve the problem. Feb 2 22:24:22 tx mysqld: Feb 2 22:24:33 tx mysqld: 150202 22:24:33 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:24:33 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:24:33 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:24:33 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:24:33 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:24:33 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:24:33 tx mysqld: doesn't support. Feb 2 22:24:33 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:24:33 tx mysqld: how you can resolve the problem. Feb 2 22:24:33 tx mysqld: Feb 2 22:24:33 tx mysqld: 150202 22:24:33 [ERROR] Cannot find or open table atest_sn5/orders_products from Feb 2 22:24:33 tx mysqld: the internal data dictionary of InnoDB though the .frm file for the Feb 2 22:24:33 tx mysqld: table exists. Maybe you have deleted and recreated InnoDB data Feb 2 22:24:33 tx mysqld: files but have forgotten to delete the corresponding .frm files Feb 2 22:24:33 tx mysqld: of InnoDB tables, or you have moved .frm files to another database? Feb 2 22:24:33 tx mysqld: or, the table contains indexes that this version of the engine Feb 2 22:24:33 tx mysqld: doesn't support. Feb 2 22:24:33 tx mysqld: See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:24:33 tx mysqld: how you can resolve the problem. Feb 2 22:24:33 tx mysqld: Feb 2 22:24:58 tx mysqld: 150202 22:24:58 InnoDB: Error: table `atest_sn5`.`orders_products` does not exist in the InnoDB internal Feb 2 22:24:58 tx mysqld: InnoDB: data dictionary though MySQL is trying to drop it. Feb 2 22:24:58 tx mysqld: InnoDB: Have you copied the .frm file of the table to the Feb 2 22:24:58 tx mysqld: InnoDB: MySQL database directory from another database? Feb 2 22:24:58 tx mysqld: InnoDB: You can look for further help from Feb 2 22:24:58 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html Feb 2 22:26:43 tx mysqld: 150202 22:26:43 InnoDB: Error creating file './atest_sn5/orders_products.ibd'. Feb 2 22:26:43 tx mysqld: 150202 22:26:43 InnoDB: Operating system error number 17 in a file operation. Feb 2 22:26:43 tx mysqld: InnoDB: Error number 17 means 'File exists'. Feb 2 22:26:43 tx mysqld: InnoDB: Some operating system error numbers are described at Feb 2 22:26:43 tx mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html Feb 2 22:26:43 tx mysqld: InnoDB: The file already exists though the corresponding table did not Feb 2 22:26:43 tx mysqld: InnoDB: exist in the InnoDB data dictionary. Have you moved InnoDB Feb 2 22:26:43 tx mysqld: InnoDB: .ibd files around without using the SQL commands Feb 2 22:26:43 tx mysqld: InnoDB: DISCARD TABLESPACE and IMPORT TABLESPACE, or did Feb 2 22:26:43 tx mysqld: InnoDB: mysqld crash in the middle of CREATE TABLE? You can Feb 2 22:26:43 tx mysqld: InnoDB: resolve the problem by removing the file './atest_sn5/orders_products.ibd' Feb 2 22:26:43 tx mysqld: InnoDB: under the 'datadir' of MySQL. Feb 2 22:30:27 tx mysqld: 150202 22:30:27 [Warning] Access denied for user 'root'@'localhost' (using password: NO) Feb 2 22:31:52 tx mysqld: 150202 22:31:52 [Warning] Aborted connection 1 to db: 'atest_sn5' user: 'test' host: 'localhost' (Unknown error) Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Warning: trying to init to the tablespace memory cache Feb 2 22:32:03 tx mysqld: InnoDB: a tablespace 12390 of name './atest_sn5/orders_products.ibd', Feb 2 22:32:03 tx mysqld: InnoDB: but a tablespace 12292 of the same name Feb 2 22:32:03 tx mysqld: InnoDB: already exists in the tablespace memory cache! Feb 2 22:32:03 tx mysqld: InnoDB: We assume that InnoDB did a crash recovery, and you had Feb 2 22:32:03 tx mysqld: InnoDB: an .ibd file for which the table did not exist in the Feb 2 22:32:03 tx mysqld: InnoDB: InnoDB internal data dictionary in the ibdata files. Feb 2 22:32:03 tx mysqld: InnoDB: We assume that you later removed the .ibd and .frm files, Feb 2 22:32:03 tx mysqld: InnoDB: and are now trying to recreate the table. We now remove the Feb 2 22:32:03 tx mysqld: InnoDB: conflicting tablespace object from the memory cache and try Feb 2 22:32:03 tx mysqld: InnoDB: the init again. Feb 2 22:32:03 tx mysqld: 150202 22:32:03 [ERROR] mysqld got signal 11 ; Feb 2 22:32:03 tx mysqld: This could be because you hit a bug. It is also possible that this binary Feb 2 22:32:03 tx mysqld: or one of the libraries it was linked against is corrupt, improperly built, Feb 2 22:32:03 tx mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: We will try our best to scrape up some info that will hopefully help Feb 2 22:32:03 tx mysqld: diagnose the problem, but since we have already crashed, Feb 2 22:32:03 tx mysqld: something is definitely wrong and this may fail. Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: Server version: 5.5.40-MariaDB-0ubuntu0.14.04.1 Feb 2 22:32:03 tx mysqld: key_buffer_size=134217728 Feb 2 22:32:03 tx mysqld: read_buffer_size=2097152 Feb 2 22:32:03 tx mysqld: max_used_connections=3 Feb 2 22:32:03 tx mysqld: max_threads=102 Feb 2 22:32:03 tx mysqld: thread_count=1 Feb 2 22:32:03 tx mysqld: It is possible that mysqld could use up to Feb 2 22:32:03 tx mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759562 K bytes of memory Feb 2 22:32:03 tx mysqld: Hope that's ok; if not, decrease some variables in the equation. Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: Thread pointer: 0x0x7f4b6dbaf000 Feb 2 22:32:03 tx mysqld: Attempting backtrace. You can use the following information to find out Feb 2 22:32:03 tx mysqld: where mysqld died. If you see no messages after this, something went Feb 2 22:32:03 tx mysqld: terribly wrong... Feb 2 22:32:03 tx mysqld: stack_bottom = 0x7f4b9ecade40 thread_stack 0x48000 Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f4b9f61570e] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f4b9f2072d7] Feb 2 22:32:03 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f4b9e2b6340] Feb 2 22:32:03 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(+0x140da6)[0x7f4b9d3deda6] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x81decd)[0x7f4b9f55cecd] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x7842a1)[0x7f4b9f4c32a1] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x789c25)[0x7f4b9f4c8c25] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x6f7258)[0x7f4b9f436258] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x6d688f)[0x7f4b9f41588f] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP24st_ha_create_information+0x77)[0x7f4b9f20e027] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1ac)[0x7f4b9f20ea3c] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cf)[0x7f4b9f17189f] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(+0x3fdc72)[0x7f4b9f13cc72] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0xbf)[0x7f4b9f13d87f] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x65b6)[0x7f4b9f0c6656] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11a)[0x7f4b9f0c6cea] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x193d)[0x7f4b9f0c8ebd] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c3)[0x7f4b9f186663] Feb 2 22:32:03 tx mysqld: /usr/sbin/mysqld(handle_one_connection+0x4a)[0x7f4b9f18675a] Feb 2 22:32:03 tx mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f4b9e2ae182] Feb 2 22:32:03 tx mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4b9d39900d] Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: Trying to get some variables. Feb 2 22:32:03 tx mysqld: Some pointers may be invalid and cause the dump to abort. Feb 2 22:32:03 tx mysqld: Query (0x7f4b68421018): is an invalid pointer Feb 2 22:32:03 tx mysqld: Connection ID (thread ID): 23 Feb 2 22:32:03 tx mysqld: Status: NOT_KILLED Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off Feb 2 22:32:03 tx mysqld: Feb 2 22:32:03 tx mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Feb 2 22:32:03 tx mysqld: information that should help you find out what is causing the crash. Feb 2 22:32:03 tx mysqld_safe: Number of processes running now: 0 Feb 2 22:32:03 tx mysqld_safe: mysqld restarted Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: The InnoDB memory heap is disabled Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Compressed tables use zlib 1.2.8 Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Using Linux native AIO Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Initializing buffer pool, size = 256.0M Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Completed initialization of buffer pool Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: highest supported file format is Barracuda. Feb 2 22:32:03 tx mysqld: InnoDB: Log scan progressed past the checkpoint lsn 89871204965 Feb 2 22:32:03 tx mysqld: 150202 22:32:03 InnoDB: Database was not shut down normally! Feb 2 22:32:03 tx mysqld: InnoDB: Starting crash recovery. Feb 2 22:32:03 tx mysqld: InnoDB: Reading tablespace information from the .ibd files... Feb 2 22:32:04 tx mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite Feb 2 22:32:04 tx mysqld: InnoDB: buffer... Feb 2 22:32:04 tx mysqld: InnoDB: Doing recovery: scanned up to log sequence number 89871237434 Feb 2 22:32:05 tx mysqld: 150202 22:32:05 InnoDB: Starting an apply batch of log records to the database... Feb 2 22:32:05 tx mysqld: InnoDB: Progress in percents: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Feb 2 22:32:05 tx mysqld: InnoDB: Apply batch completed Feb 2 22:32:05 tx mysqld: InnoDB: Last MySQL binlog file position 0 13582295, file name /var/log/mysql/mariadb-bin.001278 Feb 2 22:32:05 tx mysqld: 150202 22:32:05 InnoDB: Waiting for the background threads to start Feb 2 22:32:06 tx mysqld: 150202 22:32:06 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 89871237434 Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Note] Plugin 'FEEDBACK' is disabled. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [ERROR] Function 'ARCHIVE' already exists Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Warning] Couldn't load plugin named 'ARCHIVE' with soname 'ha_archive.so'. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [ERROR] Function 'FEDERATED' already exists Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Warning] Couldn't load plugin named 'FEDERATED' with soname 'ha_federated.so'. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [ERROR] Function 'BLACKHOLE' already exists Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Warning] Couldn't load plugin named 'BLACKHOLE' with soname 'ha_blackhole.so'. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_example.so' (errno: 0, cannot open shared object file: No such file or directory) Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Warning] Couldn't load plugin named 'EXAMPLE' with soname 'ha_example.so'. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Note] Server socket created on IP: '127.0.0.1'. Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Note] Event Scheduler: Loaded 0 events Feb 2 22:32:06 tx mysqld: 150202 22:32:06 [Note] /usr/sbin/mysqld: ready for connections. Feb 2 22:32:06 tx mysqld: Version: '5.5.40-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)