2014-05-29 10:39:12 78643 [ERROR] Table ./test/sometable has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table. 2014-05-29 10:39:12 78643 [Warning] Table ./test/sometable key_used_on_scan is 0 even though there is no primary key inside InnoDB. 2014-05-29 10:39:12 78643 [ERROR] Index key1 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html 2014-05-29 10:39:12 78643 [ERROR] Index key2 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html 2014-05-29 10:39:12 78643 [ERROR] Index key3 of test/sometable has 2 columns unique inside InnoDB, but MySQL is asking statistics for 3 columns. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html 22:39:12 UTC - mysqld got signal 11 ; 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. Please help us make Percona Server better by reporting any bugs at http://bugs.percona.com/ key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69125 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fcc5098b200 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 = 12a054e60 thread_stack 0x40000 0 mysqld 0x00000001042c3a05 my_print_stacktrace + 61 1 mysqld 0x00000001041161f1 handle_fatal_signal + 711 2 libsystem_platform.dylib 0x00007fff9a0775aa _sigtramp + 26 3 ??? 0x0000000000000001 0x0 + 1 4 mysqld 0x000000010437a1b8 _ZN11ha_innobase16records_in_rangeEjP12st_key_rangeS1_ + 468 5 mysqld 0x0000000104065042 _ZN7handler27multi_range_read_info_constEjP15st_range_seq_ifPvjPjS3_P13Cost_estimate + 456 6 mysqld 0x0000000104065cdf _ZN10DsMrr_impl16dsmrr_info_constEjP15st_range_seq_ifPvjPjS3_P13Cost_estimate + 73 7 mysqld 0x0000000104102bde _ZL18check_quick_selectP5PARAMjbP7SEL_ARGbPjS3_P13Cost_estimate + 586 8 mysqld 0x00000001040fb7f6 _ZL20get_key_scans_paramsP5PARAMP8SEL_TREEbbd + 435 9 mysqld 0x00000001040f9e1e _ZN10SQL_SELECT17test_quick_selectEP3THD6BitmapILj64EEyybN8st_order10enum_orderE + 9174 10 mysqld 0x0000000104191cd8 _ZN4JOIN8optimizeEv + 10776 11 mysqld 0x00000001041d0f66 _Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex + 657 12 mysqld 0x00000001041d0ca5 _Z13handle_selectP3THDP13select_resultm + 293 13 mysqld 0x00000001041a88c3 _ZL21execute_sqlcom_selectP3THDP10TABLE_LIST + 583 14 mysqld 0x00000001041a2c78 _Z21mysql_execute_commandP3THD + 1524 15 mysqld 0x00000001041a1b41 _Z11mysql_parseP3THDPcjP12Parser_state + 773 16 mysqld 0x000000010419f94b _Z16dispatch_command19enum_server_commandP3THDPcj + 948 17 mysqld 0x00000001041a164e _Z10do_commandP3THD + 440 18 mysqld 0x000000010416634f _Z24do_handle_one_connectionP3THD + 364 19 mysqld 0x00000001041661d6 handle_one_connection + 59 20 mysqld 0x000000010447adaf pfs_spawn_thread + 311 21 libsystem_pthread.dylib 0x00007fff900f8899 _pthread_body + 138 22 libsystem_pthread.dylib 0x00007fff900f872a _pthread_struct_init + 0 23 libsystem_pthread.dylib 0x00007fff900fcfc9 thread_start + 13 Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7fcc51803c10): is an invalid pointer Connection ID (thread ID): 1 Status: NOT_KILLED You may download the Percona Server operations manual by visiting http://www.percona.com/software/percona-server/. You may find information in the manual which will help you identify the cause of the crash. 140529 10:39:12 mysqld_safe mysqld restarted 2014-05-29 10:39:12 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2014-05-29 10:39:12 78655 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive 2014-05-29 10:39:12 78655 [Note] Plugin 'FEDERATED' is disabled. 2014-05-29 10:39:12 78655 [Note] InnoDB: The InnoDB memory heap is disabled 2014-05-29 10:39:12 78655 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-05-29 10:39:12 78655 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-05-29 10:39:12 78655 [Note] InnoDB: Using CPU crc32 instructions 2014-05-29 10:39:12 78655 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2014-05-29 10:39:12 78655 [Note] InnoDB: Completed initialization of buffer pool 2014-05-29 10:39:12 78655 [Note] InnoDB: Highest supported file format is Barracuda. 2014-05-29 10:39:12 78655 [Note] InnoDB: Log scan progressed past the checkpoint lsn 301598943581 2014-05-29 10:39:12 78655 [Note] InnoDB: Database was not shutdown normally! 2014-05-29 10:39:12 78655 [Note] InnoDB: Starting crash recovery. 2014-05-29 10:39:12 78655 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-05-29 10:39:12 78655 [Note] InnoDB: Restoring possible half-written data pages 2014-05-29 10:39:12 78655 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 301598988788 2014-05-29 10:39:12 78655 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 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 2014-05-29 10:39:13 78655 [Note] InnoDB: 128 rollback segment(s) are active. 2014-05-29 10:39:13 78655 [Note] InnoDB: Waiting for purge to start 2014-05-29 10:39:13 78655 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.13-60.3 started; log sequence number 301598988788 2014-05-29 10:39:13 78655 [Note] RSA private key file not found: /usr/local/var/mysql//private_key.pem. Some authentication plugins will not work. 2014-05-29 10:39:13 78655 [Note] RSA public key file not found: /usr/local/var/mysql//public_key.pem. Some authentication plugins will not work. 2014-05-29 10:39:13 78655 [Note] Event Scheduler: Loaded 0 events 2014-05-29 10:39:13 78655 [Note] /usr/local/Cellar/percona-server/5.6.13-rel61.0/bin/mysqld: ready for connections. Version: '5.6.13-log' socket: '/tmp/mysql.sock' port: 0 Source distribution