Created
May 9, 2017 21:38
-
-
Save alisamii/4b45e7af536c7d4c8c5657af09dcc7e2 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 170509 22:25:58 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:25:58 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 45983 ... | |
| 2017-05-09 22:25:58 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB | |
| 2017-05-09 22:25:59 140736651862976 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB | |
| 2017-05-09 22:26:00 140736651862976 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 | |
| 2017-05-09 22:26:00 140736651862976 [Warning] InnoDB: New log files created, LSN=40443083550 | |
| 2017-05-09 22:26:00 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:26:01 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:26:01 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:26:01 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:26:01 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010def2304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010d9ee5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010dd95d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010deab956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010de017ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010d9ef0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010db4e074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010db4ddba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010da95766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010da93c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:26:01 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:26:09 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:26:10 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46059 ... | |
| 2017-05-09 22:26:10 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:26:11 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:26:12 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:26:12 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:26:28 140736651862976 [Note] InnoDB: Processed 220 .ibd/.isl files | |
| 2017-05-09 22:26:44 140736651862976 [Note] InnoDB: Processed 407 .ibd/.isl files | |
| 2017-05-09 22:27:00 140736651862976 [Note] InnoDB: Processed 561 .ibd/.isl files | |
| 2017-05-09 22:27:16 140736651862976 [Note] InnoDB: Processed 1650 .ibd/.isl files | |
| 2017-05-09 22:27:32 140736651862976 [Note] InnoDB: Processed 3179 .ibd/.isl files | |
| 2017-05-09 22:27:44 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 22:27:45 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:27:45 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:27:45 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:27:45 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:27:45 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000105e27304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001059235d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000105ccad3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000105de0956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000105d367ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001059240df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000105a83074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000105a82dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001059ca766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001059c8c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:27:45 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:27:49 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:27:50 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46158 ... | |
| 2017-05-09 22:27:50 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:27:52 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:28:08 140736651862976 [Note] InnoDB: Processed 616 .ibd/.isl files | |
| 2017-05-09 22:28:21 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 22:28:21 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:28:27 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:28:27 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:28:27 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:28:27 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010d4d6304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010cfd25d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010d379d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010d48f956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010d3e57ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010cfd30df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010d132074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010d131dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010d079766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010d077c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:28:27 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:28:27 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:28:28 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46234 ... | |
| 2017-05-09 22:28:28 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:28:28 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:28:30 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:28:30 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:28:30 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:28:30 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:28:30 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010f813304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010f30f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010f6b6d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010f7cc956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010f7227ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010f3100df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010f46f074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010f46edba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010f3b6766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010f3b4c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:28:30 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:28:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:28:37 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46310 ... | |
| 2017-05-09 22:28:37 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:28:38 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:28:39 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:28:39 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:28:39 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:28:39 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:28:39 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010f99c304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010f4985d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010f83fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010f955956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010f8ab7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010f4990df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010f5f8074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010f5f7dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010f53f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010f53dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:28:39 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:28:47 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:28:47 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46384 ... | |
| 2017-05-09 22:28:47 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:28:47 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:28:48 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:28:48 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:28:48 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:28:48 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:28:48 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000102943304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010243f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001027e6d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001028fc956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001028527ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001024400df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010259f074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010259edba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001024e6766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001024e4c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:28:48 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:28:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:28:58 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46459 ... | |
| 2017-05-09 22:28:58 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:28:58 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:28:59 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:28:59 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:28:59 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:28:59 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:28:59 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000107737304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001072335d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001075dad3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001076f0956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001076467ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001072340df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107393074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107392dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001072da766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001072d8c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:28:59 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:29:08 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:29:08 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46533 ... | |
| 2017-05-09 22:29:08 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:29:09 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:29:10 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:29:10 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:29:10 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:29:10 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000107615304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001071115d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001074b8d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001075ce956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001075247ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001071120df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107271074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107270dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001071b8766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001071b6c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:29:10 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:29:19 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:29:19 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46608 ... | |
| 2017-05-09 22:29:19 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:29:20 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:29:21 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:29:21 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:29:21 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:29:21 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:29:21 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010e5af304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010e0ab5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010e452d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010e568956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010e4be7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010e0ac0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010e20b074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010e20adba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010e152766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010e150c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:29:21 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:29:30 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:29:30 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46682 ... | |
| 2017-05-09 22:29:30 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:29:30 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:29:31 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:29:32 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:29:32 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:29:32 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:29:32 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010e55d304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010e0595d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010e400d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010e516956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010e46c7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010e05a0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010e1b9074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010e1b8dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010e100766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010e0fec03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:29:32 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:29:40 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:29:40 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46757 ... | |
| 2017-05-09 22:29:40 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:29:42 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:29:43 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:29:43 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:29:43 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:29:43 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:29:44 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:29:44 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:29:44 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:29:44 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:29:44 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000101793304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010128f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000101636d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010174c956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001016a27ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001012900df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001013ef074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001013eedba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101336766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101334c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:29:44 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:29:50 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:29:51 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46833 ... | |
| 2017-05-09 22:29:51 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:29:52 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:29:52 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:29:52 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:29:52 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000100c50304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010074c5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000100af3d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000100c09956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000100b5f7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010074d0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001008ac074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001008abdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001007f3766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001007f1c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:29:52 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:01 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:01 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46910 ... | |
| 2017-05-09 22:30:01 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:01 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:02 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:02 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:02 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:02 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:02 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010991e304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010941a5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001097c1d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001098d7956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010982d7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010941b0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010957a074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000109579dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001094c1766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001094bfc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:02 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:11 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:12 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 46984 ... | |
| 2017-05-09 22:30:12 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:12 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:13 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:13 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:13 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:13 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:13 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010d75d304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010d2595d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010d600d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010d716956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010d66c7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010d25a0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010d3b9074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010d3b8dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010d300766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010d2fec03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:13 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:22 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:22 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47061 ... | |
| 2017-05-09 22:30:22 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:23 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:24 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:24 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:24 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:24 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001041c6304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000103cc25d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000104069d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010417f956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001040d57ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000103cc30df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000103e22074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000103e21dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000103d69766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000103d67c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:24 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:33 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47135 ... | |
| 2017-05-09 22:30:33 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:33 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:34 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:34 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:34 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:34 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:34 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:34 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:34 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010eddb304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010e8d75d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010ec7ed3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010ed94956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010ecea7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010e8d80df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010ea37074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010ea36dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010e97e766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010e97cc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:34 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:44 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47209 ... | |
| 2017-05-09 22:30:44 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:45 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:45 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:45 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:45 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000102371304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000101e6d5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000102214d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010232a956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001022807ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000101e6e0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101fcd074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101fccdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101f14766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101f12c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:45 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:30:54 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:30:54 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47283 ... | |
| 2017-05-09 22:30:54 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:30:54 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:30:55 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:30:55 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:30:55 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:30:55 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:30:55 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010be89304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010b9855d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010bd2cd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010be42956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010bd987ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010b9860df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010bae5074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010bae4dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010ba2c766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010ba2ac03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:30:55 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:04 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:04 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47358 ... | |
| 2017-05-09 22:31:04 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:05 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:06 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:06 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:06 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:06 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:06 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010b4ff304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010affb5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010b3a2d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010b4b8956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010b40e7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010affc0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010b15b074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010b15adba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010b0a2766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010b0a0c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:06 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:15 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:15 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47432 ... | |
| 2017-05-09 22:31:15 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:16 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:17 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:17 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:17 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:17 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000108095304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000107b915d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000107f38d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010804e956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000107fa47ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000107b920df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107cf1074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107cf0dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000107c38766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000107c36c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:17 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:26 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:26 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47506 ... | |
| 2017-05-09 22:31:26 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:26 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:27 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:27 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:27 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:27 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:27 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010aa0d304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010a5095d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010a8b0d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010a9c6956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010a91c7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010a50a0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010a669074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010a668dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010a5b0766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010a5aec03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:27 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:36 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:36 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47581 ... | |
| 2017-05-09 22:31:36 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:37 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:38 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:38 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:38 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:38 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:38 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000104d0f304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010480b5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000104bb2d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000104cc8956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000104c1e7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010480c0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010496b074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010496adba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001048b2766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001048b0c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:38 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:47 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:47 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47655 ... | |
| 2017-05-09 22:31:47 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:49 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:50 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:50 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:50 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:50 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001091d4304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000108cd05d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000109077d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010918d956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001090e37ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000108cd10df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000108e30074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000108e2fdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000108d77766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000108d75c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:50 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:31:58 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:31:58 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47729 ... | |
| 2017-05-09 22:31:58 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:31:58 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:31:59 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:31:59 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:31:59 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:31:59 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:31:59 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000108787304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001082835d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010862ad3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000108740956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001086967ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001082840df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001083e3074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001083e2dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010832a766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000108328c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:31:59 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:32:08 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:32:08 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47804 ... | |
| 2017-05-09 22:32:08 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:32:09 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:32:09 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:32:09 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:32:09 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001082d5304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000107dd15d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000108178d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010828e956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001081e47ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000107dd20df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107f31074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107f30dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000107e78766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000107e76c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:32:09 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:32:18 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:32:19 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47878 ... | |
| 2017-05-09 22:32:19 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:32:19 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:32:20 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:32:20 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:32:20 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:32:20 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000101e0b304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001019075d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000101caed3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000101dc4956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000101d1a7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001019080df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101a67074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101a66dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001019ae766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001019acc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:32:20 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:32:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:32:29 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 47952 ... | |
| 2017-05-09 22:32:29 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:32:29 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:32:30 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:32:30 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:32:30 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:32:30 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:32:30 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000109dca304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001098c65d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000109c6dd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000109d83956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000109cd97ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001098c70df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000109a26074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000109a25dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010996d766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010996bc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:32:30 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:32:39 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:32:39 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48027 ... | |
| 2017-05-09 22:32:39 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:32:40 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:32:41 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:32:41 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:32:41 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:32:41 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:32:41 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010ac3d304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010a7395d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010aae0d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010abf6956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010ab4c7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010a73a0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010a899074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010a898dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010a7e0766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010a7dec03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:32:41 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:32:49 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:32:50 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48102 ... | |
| 2017-05-09 22:32:50 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:32:51 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:32:52 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:32:52 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:32:52 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:32:52 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010b943304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010b43f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010b7e6d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010b8fc956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010b8527ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010b4400df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010b59f074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010b59edba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010b4e6766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010b4e4c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:32:52 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:00 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:00 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48176 ... | |
| 2017-05-09 22:33:00 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:00 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:01 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:01 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:01 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:01 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:01 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010ef50304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010ea4c5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010edf3d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010ef09956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010ee5f7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010ea4d0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010ebac074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010ebabdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010eaf3766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010eaf1c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:01 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:10 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:11 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48251 ... | |
| 2017-05-09 22:33:11 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:11 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:12 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:12 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:12 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:12 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:12 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000104443304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000103f3f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001042e6d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001043fc956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001043527ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000103f400df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010409f074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010409edba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000103fe6766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000103fe4c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:12 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:21 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:21 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48333 ... | |
| 2017-05-09 22:33:21 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:21 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:22 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:22 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:22 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:22 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000107db4304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001078b05d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000107c57d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000107d6d956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000107cc37ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001078b10df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107a10074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107a0fdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000107957766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000107955c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:22 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:31 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:31 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48407 ... | |
| 2017-05-09 22:33:31 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:31 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:32 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:32 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:32 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:32 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:32 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010c1ba304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010bcb65d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010c05dd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010c173956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010c0c97ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010bcb70df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010be16074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010be15dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010bd5d766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010bd5bc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:32 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:41 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:41 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48481 ... | |
| 2017-05-09 22:33:41 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:42 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:43 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:43 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:43 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:43 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010e383304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010de7f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010e226d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010e33c956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010e2927ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010de800df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010dfdf074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010dfdedba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010df26766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010df24c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:43 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:33:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:33:52 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48555 ... | |
| 2017-05-09 22:33:52 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:33:53 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:33:53 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:33:53 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:33:53 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001019c7304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001014c35d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010186ad3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000101980956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001018d67ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001014c40df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101623074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101622dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010156a766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101568c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:33:53 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:02 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:02 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48630 ... | |
| 2017-05-09 22:34:02 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:03 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:03 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:03 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:03 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000101f1b304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000101a175d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000101dbed3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000101ed4956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000101e2a7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000101a180df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101b77074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101b76dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101abe766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101abcc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:03 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:13 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:13 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48706 ... | |
| 2017-05-09 22:34:13 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:13 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:14 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:14 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:14 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:14 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:14 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000105d45304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001058415d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000105be8d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000105cfe956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000105c547ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001058420df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001059a1074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001059a0dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001058e8766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001058e6c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:14 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:23 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:23 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48781 ... | |
| 2017-05-09 22:34:23 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:24 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:25 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:25 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:25 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:25 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001057c1304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001052bd5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000105664d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010577a956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001056d07ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001052be0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010541d074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010541cdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000105364766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000105362c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:25 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:34 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:34 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48857 ... | |
| 2017-05-09 22:34:34 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:34 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:35 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:35 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:35 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:35 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:35 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:35 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:35 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:35 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010eace304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010e5ca5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010e971d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010ea87956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010e9dd7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010e5cb0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010e72a074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010e729dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010e671766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010e66fc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:35 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:44 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:45 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 48943 ... | |
| 2017-05-09 22:34:45 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:45 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:45 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:46 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:46 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:46 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:46 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001007ec304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001002e85d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010068fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001007a5956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001006fb7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001002e90df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000100448074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000100447dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010038f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010038dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:46 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:34:55 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:34:55 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49034 ... | |
| 2017-05-09 22:34:56 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:34:57 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:34:57 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:34:58 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:34:58 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:34:58 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:34:58 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001074bd304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000106fb95d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000107360d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000107476956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001073cc7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000106fba0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000107119074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000107118dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000107060766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010705ec03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:34:58 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:35:06 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:35:06 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49159 ... | |
| 2017-05-09 22:35:06 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:35:07 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:35:07 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:35:08 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:35:08 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:35:08 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:35:08 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:35:08 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001023bc304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000101eb85d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010225fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000102375956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001022cb7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000101eb90df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000102018074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000102017dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101f5f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101f5dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:35:08 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:35:22 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:35:22 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49531 ... | |
| 2017-05-09 22:35:22 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:35:23 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:35:23 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:35:24 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:35:24 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:35:24 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:35:24 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010b494304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010af905d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010b337d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010b44d956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010b3a37ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010af910df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010b0f0074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010b0efdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010b037766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010b035c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:35:24 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:35:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:35:33 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49617 ... | |
| 2017-05-09 22:35:33 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:35:33 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:35:33 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:35:34 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:35:34 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:35:34 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:35:34 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:35:34 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000102129304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000101c255d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000101fccd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001020e2956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001020387ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000101c260df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101d85074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101d84dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101ccc766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101ccac03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:35:34 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:35:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:35:44 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49703 ... | |
| 2017-05-09 22:35:44 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:35:44 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:35:44 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:35:45 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:35:45 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:35:45 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:35:45 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001079df304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001074db5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000107882d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000107998956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001078ee7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001074dc0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010763b074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010763adba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000107582766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000107580c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:35:45 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:35:54 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:35:54 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 49933 ... | |
| 2017-05-09 22:35:54 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:35:54 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:35:54 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:35:55 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:35:55 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:35:55 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:35:55 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:35:55 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000104105304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000103c015d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000103fa8d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001040be956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001040147ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000103c020df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000103d61074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000103d60dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000103ca8766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000103ca6c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:35:55 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:36:04 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:36:04 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 50019 ... | |
| 2017-05-09 22:36:04 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:36:05 140736651862976 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1 | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:36:05 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:36:06 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:36:06 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:36:06 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:36:06 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000100f7a304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000100a765d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000100e1dd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000100f33956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000100e897ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000100a770df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000100bd6074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000100bd5dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000100b1d766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000100b1bc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:36:06 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:39:42 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:39:42 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 50456 ... | |
| 2017-05-09 22:39:42 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:39:43 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:39:43 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:39:43 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:39:43 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001008d6304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001003d25d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000100779d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010088f956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001007e57ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001003d30df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000100532074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000100531dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000100479766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000100477c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:39:44 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:39:53 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:39:53 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 50916 ... | |
| 2017-05-09 22:39:53 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:39:53 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:39:54 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:39:54 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:39:54 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:39:54 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:39:54 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010c373304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010be6f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010c216d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010c32c956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010c2827ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010be700df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010bfcf074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010bfcedba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010bf16766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010bf14c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:39:54 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:03 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:03 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 50990 ... | |
| 2017-05-09 22:40:03 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:40:04 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:40:04 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:40:04 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:40:04 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000105554304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001050505d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001053f7d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010550d956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001054637ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001050510df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001051b0074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001051afdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001050f7766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001050f5c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:40:04 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:14 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51067 ... | |
| 2017-05-09 22:40:14 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:40:15 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:40:15 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:40:15 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:40:15 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010cc91304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010c78d5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010cb34d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010cc4a956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010cba07ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010c78e0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010c8ed074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010c8ecdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010c834766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010c832c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:40:16 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:24 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:24 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51142 ... | |
| 2017-05-09 22:40:24 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:40:25 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:40:31 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:40:31 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:40:31 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:40:31 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:40:31 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010cfea304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010cae65d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010ce8dd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010cfa3956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010cef97ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010cae70df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010cc46074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010cc45dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010cb8d766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010cb8bc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:40:31 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:35 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:36 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51217 ... | |
| 2017-05-09 22:40:36 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:40:38 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:40:46 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:40:47 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:40:47 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:40:47 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:40:47 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000102bf2304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001026ee5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000102a95d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000102bab956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x0000000102b017ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001026ef0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010284e074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010284ddba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000102795766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000102793c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:40:47 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:47 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:47 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51292 ... | |
| 2017-05-09 22:40:47 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:40:48 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:40:49 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:40:49 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:40:59 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:40:59 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:40:59 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:40:59 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:40:59 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001086f5304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001081f15d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000108598d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001086ae956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001086047ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001081f20df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000108351074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000108350dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000108298766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000108296c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:40:59 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:40:59 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:40:59 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51366 ... | |
| 2017-05-09 22:40:59 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:00 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:00 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:00 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:00 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001046a6304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001041a25d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000104549d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010465f956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001045b57ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001041a30df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000104302074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000104301dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000104249766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000104247c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:00 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:41:09 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:41:09 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51440 ... | |
| 2017-05-09 22:41:09 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:10 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:10 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:10 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:10 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010af4e304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010aa4a5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010adf1d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010af07956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010ae5d7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010aa4b0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010abaa074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010aba9dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010aaf1766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010aaefc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:10 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:41:20 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:41:20 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51514 ... | |
| 2017-05-09 22:41:20 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:21 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:21 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:21 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:21 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010addc304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010a8d85d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010ac7fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010ad95956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010aceb7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010a8d90df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010aa38074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010aa37dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010a97f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010a97dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:21 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:41:30 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:41:31 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51588 ... | |
| 2017-05-09 22:41:31 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:31 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:32 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:32 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:32 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:32 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000104786304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001042825d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000104629d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010473f956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001046957ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001042830df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001043e2074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001043e1dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000104329766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000104327c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:32 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:41:41 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:41:41 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51662 ... | |
| 2017-05-09 22:41:41 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:42 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:43 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:43 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:43 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:43 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010d2f4304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010cdf05d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010d197d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010d2ad956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010d2037ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010cdf10df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010cf50074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010cf4fdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010ce97766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010ce95c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:43 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:41:52 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:41:52 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51737 ... | |
| 2017-05-09 22:41:52 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:41:52 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:41:53 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:41:53 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:41:53 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:41:53 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:41:53 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000101910304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010140c5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001017b3d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001018c9956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010181f7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010140d0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010156c074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010156bdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x00000001014b3766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x00000001014b1c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:41:53 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:42:02 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:42:02 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51813 ... | |
| 2017-05-09 22:42:02 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:42:03 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:42:04 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:42:04 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:42:04 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:42:04 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:42:04 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010ba2b304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010b5275d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010b8ced3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010b9e4956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010b93a7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010b5280df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010b687074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010b686dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010b5ce766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010b5ccc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:42:04 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:42:13 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:42:13 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51888 ... | |
| 2017-05-09 22:42:13 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:42:13 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:42:14 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:42:14 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:42:14 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:42:14 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:42:14 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010a503304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000109fff5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010a3a6d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010a4bc956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010a4127ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010a0000df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010a15f074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010a15edba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010a0a6766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010a0a4c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:42:14 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:42:23 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:42:23 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 51962 ... | |
| 2017-05-09 22:42:23 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:42:24 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:42:24 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:42:24 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:42:24 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010e406304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010df025d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010e2a9d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010e3bf956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010e3157ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010df030df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010e062074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010e061dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010dfa9766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010dfa7c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:42:24 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:42:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:42:34 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52044 ... | |
| 2017-05-09 22:42:34 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:42:34 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:42:44 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:42:44 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:42:44 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:42:44 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:42:44 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010f921304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010f41d5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010f7c4d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010f8da956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010f8307ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010f41e0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010f57d074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010f57cdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010f4c4766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010f4c2c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:42:44 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:42:45 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:42:45 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52118 ... | |
| 2017-05-09 22:42:45 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:42:46 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:43:00 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:43:00 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:43:00 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:43:00 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:43:00 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000102167304 my_print_stacktrace + 60 | |
| 0 mysqld 0x0000000101c635d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010200ad3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000102120956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001020767ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x0000000101c640df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x0000000101dc3074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x0000000101dc2dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000101d0a766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000101d08c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:43:00 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:43:00 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:43:01 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52194 ... | |
| 2017-05-09 22:43:01 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:43:01 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:43:16 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 22:43:16 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:43:16 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:43:16 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:43:16 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:43:16 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000110336304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010fe325d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x00000001101d9d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x00000001102ef956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001102457ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010fe330df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010ff92074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010ff91dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010fed9766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010fed7c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:43:16 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:43:17 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:43:17 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52271 ... | |
| 2017-05-09 22:43:17 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:43:18 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:43:18 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:43:18 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:43:18 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x00000001057c0304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001052bc5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000105663d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000105779956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001056cf7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001052bd0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010541c074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010541bdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000105363766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000105361c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:43:18 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:43:26 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:43:27 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52429 ... | |
| 2017-05-09 22:43:27 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:43:28 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:43:29 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:43:29 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:43:29 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:43:29 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:43:29 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010f48c304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010ef885d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010f32fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010f445956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010f39b7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010ef890df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010f0e8074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010f0e7dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010f02f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010f02dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:43:29 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:43:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:43:38 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52514 ... | |
| 2017-05-09 22:43:38 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:43:38 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:43:54 140736651862976 [Note] InnoDB: Processed 4334 .ibd/.isl files | |
| 2017-05-09 22:43:56 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 22:43:56 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:43:56 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:43:56 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:43:56 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:43:56 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010f7ee304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010f2ea5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010f691d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010f7a7956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010f6fd7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010f2eb0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010f44a074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010f449dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010f391766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010f38fc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:43:56 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 22:43:57 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 22:43:57 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 52589 ... | |
| 2017-05-09 22:43:57 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 22:43:57 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 22:44:10 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 22:44:10 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 22:44:10 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 22:44:10 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 22:44:10 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x0000000100873304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010036f5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x0000000100716d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010082c956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001007827ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001003700df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001004cf074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001004cedba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x0000000100416766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x0000000100414c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 22:44:10 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended | |
| 170509 23:26:10 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 23:26:11 140736651862976 [Note] /usr/local/opt/mariadb/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 54097 ... | |
| 2017-05-09 23:26:11 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 23:26:11 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 23:26:26 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 23:26:26 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 23:26:26 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 23:26:26 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 23:26:26 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 23:26:26 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010ddb1304 my_print_stacktrace + 60 | |
| 0 mysqld 0x000000010d8ad5d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010dc54d3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x000000010dd6a956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x000000010dcc07ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x000000010d8ae0df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x000000010da0d074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x000000010da0cdba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010d954766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010d952c03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 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. | |
| 170509 23:26:31 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql | |
| 2017-05-09 23:26:32 140736651862976 [Note] /usr/local/Cellar/mariadb/10.1.23/bin/mysqld (mysqld 10.1.23-MariaDB) starting as process 54447 ... | |
| 2017-05-09 23:26:32 140736651862976 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Using mutexes to ref count buffer pool pages | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: The InnoDB memory heap is disabled | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Compressed tables use zlib 1.2.8 | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Using SSE crc32 instructions | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Initializing buffer pool, size = 128.0M | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Completed initialization of buffer pool | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: Highest supported file format is Barracuda. | |
| 2017-05-09 23:26:33 140736651862976 [Note] InnoDB: The log sequence numbers 40443083550 and 40443083550 in ibdata files do not match the log sequence number 40443083788 in the ib_logfiles! | |
| 2017-05-09 23:26:49 140736651862976 [Note] InnoDB: Processed 1881 .ibd/.isl files | |
| 2017-05-09 23:27:05 140736651862976 [Note] InnoDB: Processed 3399 .ibd/.isl files | |
| 2017-05-09 23:27:07 140736651862976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer... | |
| 2017-05-09 23:27:07 140736651862976 [Note] InnoDB: Read redo log up to LSN=40443084288 | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| InnoDB: wrong number of columns in SYS_INDEXES record | |
| 2017-05-09 23:27:07 140736651862976 [Note] InnoDB: Creating tablespace and datafile system tables. | |
| 2017-05-09 23:27:07 140736651862976 [ERROR] InnoDB: Creation of SYS_TABLESPACES and SYS_DATAFILES has failed with error 18. Tablespace is full. Dropping incompletely created tables. | |
| 2017-05-09 23:27:07 7fffce2423c0 InnoDB: Assertion failure in thread 140736651862976 in file dict0crea.cc line 1903 | |
| InnoDB: Failing assertion: err == DB_OUT_OF_FILE_SPACE || err == DB_TOO_MANY_CONCURRENT_TRXS | |
| 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. | |
| 170509 23:27:07 [ERROR] 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. | |
| To report this bug, see https://mariadb.com/kb/en/reporting-bugs | |
| 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. | |
| Server version: 10.1.23-MariaDB | |
| key_buffer_size=134217728 | |
| read_buffer_size=131072 | |
| max_used_connections=0 | |
| max_threads=153 | |
| thread_count=0 | |
| It is possible that mysqld could use up to | |
| key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 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 = 0x0 thread_stack 0x48400 | |
| 0 mysqld 0x000000010689c304 my_print_stacktrace + 60 | |
| 0 mysqld 0x00000001063985d8 handle_fatal_signal + 684 | |
| 0 libsystem_platform.dylib 0x00007fffc54edb3a _sigtramp + 26 | |
| 0 libsystem_notify.dylib 0x00007fffc54e7285 registration_node_release + 40 | |
| 0 libsystem_c.dylib 0x00007fffc5372420 abort + 129 | |
| 0 mysqld 0x000000010673fd3a _Z40dict_create_add_tablespace_to_dictionarymPKcmS0_P5trx_tb + 0 | |
| 0 mysqld 0x0000000106855956 _Z34innobase_start_or_create_for_mysqlv + 7160 | |
| 0 mysqld 0x00000001067ab7ed _ZL13innobase_initPv + 2996 | |
| 0 mysqld 0x00000001063990df _Z24ha_initialize_handlertonP13st_plugin_int + 94 | |
| 0 mysqld 0x00000001064f8074 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 351 | |
| 0 mysqld 0x00000001064f7dba _Z11plugin_initPiPPci + 2881 | |
| 0 mysqld 0x000000010643f766 _ZL22init_server_componentsv + 1790 | |
| 0 mysqld 0x000000010643dc03 _Z11mysqld_mainiPPc + 9583 | |
| 0 libdyld.dylib 0x00007fffc52de235 start + 1 | |
| 0 ??? 0x0000000000000006 0x0 + 6 | |
| 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. | |
| 170509 23:27:07 mysqld_safe mysqld from pid file /usr/local/var/mysql/Alis-iMac.local.pid ended |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment