160707 1:44:49 InnoDB: Assertion failure in thread 139768130299648 in file btr0pcur.c line 430 InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor)) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 01:44:49 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=131 max_threads=1000 thread_count=117 connection_count=117 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2195723 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x71fff00 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 7f1e4dc1dd98 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x78f11e] /usr/libexec/mysqld(handle_fatal_signal+0x493)[0x677203] /lib64/libpthread.so.0(+0xf7e0)[0x7f1ee3e067e0] /lib64/libc.so.6(gsignal+0x35)[0x7f1ee224b5e5] /lib64/libc.so.6(abort+0x175)[0x7f1ee224cdc5] /usr/libexec/mysqld[0x85ba2b] /usr/libexec/mysqld[0x815134] /usr/libexec/mysqld[0x8158f0] /usr/libexec/mysqld[0x7f5a4c] /usr/libexec/mysqld[0x5a1139] /usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x71)[0x5ac1c1] /usr/libexec/mysqld[0x5a168f] /usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x7e)[0x5ac1ce] /usr/libexec/mysqld[0x5a168f] /usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x7e)[0x5ac1ce] /usr/libexec/mysqld[0x5acad7] /usr/libexec/mysqld(_ZN4JOIN4execEv+0x4cb)[0x5be24b] /usr/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x162)[0x5bffc2] /usr/libexec/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x17c)[0x5c0a4c] /usr/libexec/mysqld[0x57f987] /usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x206b)[0x58563b] /usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1bb)[0x587dab] /usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1c4d)[0x58a1ad] /usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0xd2)[0x61bcc2] /usr/libexec/mysqld(handle_one_connection+0x50)[0x61bdd0] /lib64/libpthread.so.0(+0x7aa1)[0x7f1ee3dfeaa1] /lib64/libc.so.6(clone+0x6d)[0x7f1ee2301aad] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f1e2c017110): is an invalid pointer Connection ID (thread ID): 80 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 160707 01:44:49 mysqld_safe Number of processes running now: 0 160707 01:44:49 mysqld_safe mysqld restarted 160707 1:44:49 [Warning] Using unique option prefix max_connection instead of max_connections is deprecated and will be removed in a future release. Please use the full name instead. 160707 1:44:49 [Note] /usr/libexec/mysqld (mysqld 5.5.49) starting as process 12300 ... 160707 1:44:49 [Note] Plugin 'FEDERATED' is disabled. 160707 1:44:49 InnoDB: The InnoDB memory heap is disabled 160707 1:44:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 160707 1:44:49 InnoDB: Compressed tables use zlib 1.2.3 160707 1:44:49 InnoDB: Using Linux native AIO 160707 1:44:49 InnoDB: Initializing buffer pool, size = 2.0G 160707 1:44:50 InnoDB: Completed initialization of buffer pool 160707 1:44:50 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 99851472889 160707 1:44:50 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 99851718391 160707 1:44:50 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 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 InnoDB: Apply batch completed 160707 1:44:50 InnoDB: Waiting for the background threads to start 160707 1:44:51 InnoDB: 5.5.49 started; log sequence number 99851718391 160707 1:44:51 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 160707 1:44:51 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 160707 1:44:51 [Note] Server socket created on IP: '0.0.0.0'. 160707 1:44:51 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure 160707 1:44:51 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure 160707 1:44:51 [Note] Event Scheduler: Loaded 0 events 160707 1:44:51 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.49' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 160707 1:44:54 [Warning] IP address '10.41.41.18' could not be resolved: Name or service not known 160707 3:18:01 [ERROR] Invalid (old?) table or database name 'lost+found' InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 230605. InnoDB: You may have to recover from a backup.