100908 15:27:24 InnoDB: Assertion failure in thread 1236412768 in file dict/dict0dict.c line 4854 InnoDB: Failing assertion: new_index 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.1/en/forcing-recovery.html InnoDB: about forcing recovery. 100908 15:27:24 - 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=268435456 read_buffer_size=2097152 max_used_connections=59 max_threads=600 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6412622 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2afb6d2540 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 = 0x49b22110 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x865d3e] /usr/sbin/mysqld(handle_segfault+0x322)[0x5ae182] /lib64/tls/libpthread.so.0[0x30df30c790] /lib64/tls/libc.so.6(gsignal+0x3d)[0x30dea2e32d] /lib64/tls/libc.so.6(abort+0xfe)[0x30dea2fb2e] /usr/sbin/mysqld[0x7e438f] /usr/sbin/mysqld[0x771757] /usr/sbin/mysqld[0x72ffee] /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb+0x1f15)[0x6a3a65] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x178e)[0x5bdaae] /usr/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x493)[0x5c2083] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x403)[0x5c24a3] /usr/sbin/mysqld(_Z10do_commandP3THD+0x120)[0x5c36b0] /usr/sbin/mysqld(handle_one_connection+0x7a2)[0x5b6182] /lib64/tls/libpthread.so.0[0x30df306317] /lib64/tls/libc.so.6(__clone+0x73)[0x30deac9fc3] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x2aee1bc840 is an invalid pointer thd->thread_id=8669908 thd->killed=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. mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `! "Aborted: pure virtual method called."' failed. mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `! "Aborted: pure virtual method called."' failed. 100908 15:27:24 mysqld_safe Number of processes running now: 0 100908 15:27:24 mysqld_safe mysqld restarted 100908 15:27:24 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.3 100908 15:27:24 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 56403668148 100908 15:27:24 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 56403708520 100908 15:27:25 InnoDB: Starting an apply batch of log records to the database... 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 9 5 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 744651058, file name ./mysql-bin.000116 100908 15:27:26 InnoDB: Assertion failure in thread 182894086976 in file dict/dict0dict.c line 4854 InnoDB: Failing assertion: new_index 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.1/en/forcing-recovery.html InnoDB: about forcing recovery. 100908 15:27:26 - 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=268435456 read_buffer_size=2097152 max_used_connections=0 max_threads=600 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6412622 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 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 = (nil) thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x865d3e] /usr/sbin/mysqld(handle_segfault+0x322)[0x5ae182] /lib64/tls/libpthread.so.0[0x30df30c790] /lib64/tls/libc.so.6(gsignal+0x3d)[0x30dea2e32d] /lib64/tls/libc.so.6(abort+0xfe)[0x30dea2fb2e] /usr/sbin/mysqld[0x7e438f] /usr/sbin/mysqld[0x771757] /usr/sbin/mysqld[0x773b05] /usr/sbin/mysqld[0x747d89] /usr/sbin/mysqld[0x792c00] /usr/sbin/mysqld[0x725bc1] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x31)[0x68b5d1] /usr/sbin/mysqld[0x706a2d] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x73a)[0x7091da] /usr/sbin/mysqld[0x5b013f] /usr/sbin/mysqld(main+0x6b5)[0x5b1585] /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x30dea1c4cb] /usr/sbin/mysqld[0x4fa89a] 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. 100908 15:27:26 mysqld_safe mysqld from pid file /var/lib/mysql/freya.pid ended