2015-11-14 15:20:05 30c347cd700 InnoDB: error clustered record for sec rec not found InnoDB: index `option_name` of table `database_name`.`wp_options` InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 21; hex 5f7472616e7369656e745f646f696e675f63726f6e; asc _transient_doing_cron;; 1: len 8; hex 000000000008611d; asc a ;; InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0 0: len 8; hex 00000000000000c0; asc ;; 1: len 6; hex 000012081875; asc u;; 2: len 7; hex a5000004f708a8; asc ;; 3: len 11; hex 66726d5f6f7074696f6e73; asc frm_options;; 4: len 30; hex 4f3a31313a2246726d53657474696e6773223a33363a7b733a343a226d65; asc O:11:"FrmSettings":36:{s:4:"me; (total 1514 bytes); 5: len 3; hex 74616d; asc tam;; TRANSACTION 322457650, ACTIVE 0 sec starting index read mysql tables in use 1, locked 0 MySQL thread id 5016500, OS thread handle 0x30c347cd700, query id 306190655 x.x.x.x username statistics SELECT option_value FROM wp_options WHERE option_name = '_transient_doing_cron' LIMIT 1 InnoDB: Submit a detailed bug report to http://bugs.mysql.com 2015-11-14 15:20:05 30c347cd700 InnoDB: error clustered record for sec rec not found InnoDB: index `option_name` of table `database_name`.`wp_options` InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 30; hex 5f7472616e7369656e745f74696d656f75745f325f5f3937343831383833; asc _transient_timeout_2__97481883; (total 31 bytes); 1: len 8; hex 0000000000086110; asc a ;; InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0 0: len 8; hex 00000000000000c0; asc ;; 1: len 6; hex 000012081875; asc u;; 2: len 7; hex a5000004f708a8; asc ;; 3: len 11; hex 66726d5f6f7074696f6e73; asc frm_options;; 4: len 30; hex 4f3a31313a2246726d53657474696e6773223a33363a7b733a343a226d65; asc O:11:"FrmSettings":36:{s:4:"me; (total 1514 bytes); 5: len 3; hex 74616d; asc tam;; TRANSACTION 322457651, ACTIVE 0 sec starting index read mysql tables in use 1, locked 1 2 lock struct(s), heap size 360, 1 row lock(s) MySQL thread id 5016500, OS thread handle 0x30c347cd700, query id 306190656 x.x.x.x username updating UPDATE `wp_options` SET `option_value` = '1447545005' WHERE `option_name` = '_transient_timeout_2__974818834' InnoDB: Submit a detailed bug report to http://bugs.mysql.com 2015-11-14 15:20:05 30c347cd700 InnoDB: error clustered record for sec rec not found InnoDB: index `option_name` of table `database_name`.`wp_options` InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 30; hex 5f7472616e7369656e745f74696d656f75745f325f5f3533363438333035; asc _transient_timeout_2__53648305; (total 31 bytes); 1: len 8; hex 0000000000086112; asc a ;; InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0 0: len 8; hex 00000000000000c0; asc ;; 1: len 6; hex 000012081875; asc u;; 2: len 7; hex a5000004f708a8; asc ;; 3: len 11; hex 66726d5f6f7074696f6e73; asc frm_options;; 4: len 30; hex 4f3a31313a2246726d53657474696e6773223a33363a7b733a343a226d65; asc O:11:"FrmSettings":36:{s:4:"me; (total 1514 bytes); 5: len 3; hex 74616d; asc tam;; TRANSACTION 322457652, ACTIVE 0 sec starting index read mysql tables in use 1, locked 1 2 lock struct(s), heap size 360, 1 row lock(s) MySQL thread id 5016500, OS thread handle 0x30c347cd700, query id 306190657 x.x.x.x username updating UPDATE `wp_options` SET `option_value` = '1447545005' WHERE `option_name` = '_transient_timeout_2__536483053' InnoDB: Submit a detailed bug report to http://bugs.mysql.com 2015-11-14 15:20:05 30c347cd700 InnoDB: error clustered record for sec rec not found InnoDB: index `option_name` of table `database_name`.`wp_options` InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 30; hex 5f7472616e7369656e745f74696d656f75745f325f5f3937343831383833; asc _transient_timeout_2__97481883; (total 31 bytes); 1: len 8; hex 0000000000086110; asc a ;; InnoDB: clust index record PHYSICAL RECORD: n_fields 6; compact format; info bits 0 0: len 8; hex 00000000000000c0; asc ;; 1: len 6; hex 000012081875; asc u;; 2: len 7; hex a5000004f708a8; asc ;; 3: len 11; hex 66726d5f6f7074696f6e73; asc frm_options;; 4: len 30; hex 4f3a31313a2246726d53657474696e6773223a33363a7b733a343a226d65; asc O:11:"FrmSettings":36:{s:4:"me; (total 1514 bytes); 5: len 3; hex 74616d; asc tam;; TRANSACTION 322457653, ACTIVE 0 sec starting index read mysql tables in use 1, locked 1 2 lock struct(s), heap size 360, 1 row lock(s) MySQL thread id 5016500, OS thread handle 0x30c347cd700, query id 306190658 x.x.x.x username updating UPDATE `wp_options` SET `option_value` = '1447545005' WHERE `option_name` = '_transient_timeout_2__974818834' InnoDB: Submit a detailed bug report to http://bugs.mysql.com InnoDB: Error: trying to access page number 1600414438 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 2015-11-14 15:20:17 30c0121d700 InnoDB: Assertion failure in thread 3350093485824 in file fil0fil.cc line 5608 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.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 23:20:17 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=33554432 read_buffer_size=1048576 max_used_connections=47 max_threads=1200 thread_count=5 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2505677 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x308d7d0 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 = 30c0121ce78 thread_stack 0x40000 /path/to/mysql/triodia/mysqld--triodia(my_print_stacktrace+0x29)[0x86b8f9] /path/to/mysql/triodia/mysqld--triodia(handle_fatal_signal+0x35b)[0x647b1b] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x30c33f15cb0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x30c3336c0d5] /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x30c3336f83b] /path/to/mysql/triodia/mysqld--triodia[0x9fb941] /path/to/mysql/triodia/mysqld--triodia[0x9c976a] /path/to/mysql/triodia/mysqld--triodia[0x9ca357] /path/to/mysql/triodia/mysqld--triodia[0x9b8569] /path/to/mysql/triodia/mysqld--triodia[0x977b43] /path/to/mysql/triodia/mysqld--triodia[0x97805f] /path/to/mysql/triodia/mysqld--triodia[0x96082c] /path/to/mysql/triodia/mysqld--triodia[0x9581c3] /path/to/mysql/triodia/mysqld--triodia[0x8ce505] /path/to/mysql/triodia/mysqld--triodia(_ZN7handler11ha_rnd_nextEPh+0x9c)[0x5a93dc] /path/to/mysql/triodia/mysqld--triodia(_Z13rr_sequentialP11READ_RECORD+0x14)[0x7bcb04] /path/to/mysql/triodia/mysqld--triodia(_Z10sub_selectP4JOINP13st_join_tableb+0x239)[0x695f79] /path/to/mysql/triodia/mysqld--triodia(_ZN4JOIN4execEv+0x2c4)[0x694ce4] /path/to/mysql/triodia/mysqld--triodia(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x295)[0x6d8635] /path/to/mysql/triodia/mysqld--triodia(_Z13handle_selectP3THDP13select_resultm+0x197)[0x6d8ee7] /path/to/mysql/triodia/mysqld--triodia[0x5787de] /path/to/mysql/triodia/mysqld--triodia(_Z21mysql_execute_commandP3THD+0x154a)[0x6b4f0a] /path/to/mysql/triodia/mysqld--triodia(_Z11mysql_parseP3THDPcjP12Parser_state+0x360)[0x6b97d0] /path/to/mysql/triodia/mysqld--triodia(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1b95)[0x6bb3f5] /path/to/mysql/triodia/mysqld--triodia(_Z24do_handle_one_connectionP3THD+0x1a6)[0x68dba6] /path/to/mysql/triodia/mysqld--triodia(handle_one_connection+0x40)[0x68dc00] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x30c33f0de9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x30c3342938d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (30ba81cb150): is an invalid pointer Connection ID (thread ID): 5016551 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. 151114 15:20:17 mysqld_safe Number of processes running now: 0 151114 15:20:17 mysqld_safe mysqld restarted 2015-11-14 15:20:17 0 [Note] /path/to/mysql/triodia/mysqld--triodia (mysqld 5.6.25-log) starting as process 20452 ... 2015-11-14 15:20:17 20452 [Note] Plugin 'FEDERATED' is disabled. 2015-11-14 15:20:18 20452 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-11-14 15:20:18 20452 [Note] InnoDB: The InnoDB memory heap is disabled 2015-11-14 15:20:18 20452 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-11-14 15:20:18 20452 [Note] InnoDB: Memory barrier is not used 2015-11-14 15:20:18 20452 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-11-14 15:20:18 20452 [Note] InnoDB: Using CPU crc32 instructions 2015-11-14 15:20:18 20452 [Note] InnoDB: Initializing buffer pool, size = 512.0M 2015-11-14 15:20:18 20452 [Note] InnoDB: Completed initialization of buffer pool 2015-11-14 15:20:18 20452 [Note] InnoDB: Highest supported file format is Barracuda. 2015-11-14 15:20:18 20452 [Note] InnoDB: Log scan progressed past the checkpoint lsn 77722566850 2015-11-14 15:20:18 20452 [Note] InnoDB: Database was not shutdown normally! 2015-11-14 15:20:18 20452 [Note] InnoDB: Starting crash recovery. 2015-11-14 15:20:18 20452 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-11-14 15:20:32 20452 [Note] InnoDB: Restoring possible half-written data pages 2015-11-14 15:20:32 20452 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 77722567415 2015-11-14 15:20:32 20452 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 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 2015-11-14 15:20:33 20452 [Note] InnoDB: 128 rollback segment(s) are active. 2015-11-14 15:20:33 20452 [Note] InnoDB: Waiting for purge to start 2015-11-14 15:20:33 20452 [Note] InnoDB: 5.6.25 started; log sequence number 77722567415 2015-11-14 15:20:33 20452 [Note] Server hostname (bind-address): 'x.x.x.x'; port: 3306 2015-11-14 15:20:33 20452 [Note] - 'x.x.x.x' resolves to 'x.x.x.x'; 2015-11-14 15:20:33 20452 [Note] Server socket created on IP: 'x.x.x.x'.