130517 15:58:57 mysqld_safe Starting mysqld daemon with databases from /home/var/lib/mysql 2013-05-17 15:59:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2013-05-17 15:59:05 12504 [Note] InnoDB: The InnoDB memory heap is disabled 2013-05-17 15:59:05 12504 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2013-05-17 15:59:05 12504 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-05-17 15:59:05 12504 [Note] InnoDB: CPU does not support crc32 instructions 2013-05-17 15:59:05 12504 [Note] InnoDB: Using Linux native AIO 2013-05-17 15:59:05 12504 [Note] InnoDB: Initializing buffer pool, size = 40.0G 2013-05-17 15:59:07 12504 [Note] InnoDB: Completed initialization of buffer pool 2013-05-17 15:59:07 12504 [Note] InnoDB: Highest supported file format is Barracuda. 2013-05-17 15:59:10 12504 [Warning] Invalid (old?) table or database name '#sql5307_9777_c' 2013-05-17 15:59:10 7f91b5da8720 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 2013-05-17 15:59:10 12504 [ERROR] InnoDB: Could not find a valid tablespace file for 'tmp/#sql5307_9777_c'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue. 2013-05-17 15:59:10 12504 [ERROR] InnoDB: Tablespace open failed for '"tmp".', ignored. 2013-05-17 15:59:10 12504 [Warning] Invalid (old?) table or database name '#sql5307_9777_c' 2013-05-17 15:59:10 7f91b5da8720 InnoDB: Assertion failure in thread 140263797983008 in file pars0pars.cc line 865 InnoDB: Failing assertion: sym_node->table != NULL 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. 13:59:10 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=8388608 max_used_connections=0 max_threads=3002 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49233848 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 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 = 0 thread_stack 0x40000 /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(my_print_stacktrace+0x35)[0x8da155] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(handle_fatal_signal+0x3fb)[0x65788b] /lib64/libpthread.so.0(+0xf500)[0x7f91b5991500] /lib64/libc.so.6(gsignal+0x35)[0x7f91b463d8a5] /lib64/libc.so.6(abort+0x175)[0x7f91b463f085] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9a4d02] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9a6569] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(_Z7yyparsev+0x76a)[0xabc66a] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9a55b7] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9ab020] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9d0521] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9d1815] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x97f79a] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x9f87ba] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x940d7d] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x46)[0x589d16] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x6de910] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(_Z11plugin_initPiPPci+0x80d)[0x6df9ad] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x580cfa] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld(_Z11mysqld_mainiPPc+0x31c)[0x581b5c] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f91b4629cdd] /usr/local/Percona-Server-5.6.10-alpha60.2-324.Linux.x86_64/bin/mysqld[0x576509] 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. 130517 15:59:12 mysqld_safe mysqld from pid file /home/var/lib/mysql/mysqld.pid ended