Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Last login: Mon Jul 17 16:33:18 on ttys001
- ➜ ~ mysqld
- 2017-07-17T14:58:35.788882Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
- 2017-07-17T14:58:35.789878Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
- 2017-07-17T14:58:35.790849Z 0 [Note] mysqld (mysqld 5.7.18) starting as process 24009 ...
- 2017-07-17T14:58:35.804059Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
- 2017-07-17T14:58:35.814209Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
- 2017-07-17T14:58:35.814246Z 0 [Note] InnoDB: Uses event mutexes
- 2017-07-17T14:58:35.814252Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
- 2017-07-17T14:58:35.814261Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2017-07-17T14:58:35.815418Z 0 [Note] InnoDB: Number of pools: 1
- 2017-07-17T14:58:35.819221Z 0 [Note] InnoDB: Using CPU crc32 instructions
- 2017-07-17T14:58:35.821021Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
- 2017-07-17T14:58:35.833641Z 0 [Note] InnoDB: Completed initialization of buffer pool
- 2017-07-17T14:58:35.851639Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
- 2017-07-17T14:58:35.853509Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 212319904
- 2017-07-17T14:58:35.853534Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 212320189
- 2017-07-17T14:58:35.853798Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 212320189
- 2017-07-17T14:58:35.853843Z 0 [Note] InnoDB: Database was not shutdown normally!
- 2017-07-17T14:58:35.853855Z 0 [Note] InnoDB: Starting crash recovery.
- 2017-07-17T14:58:36.155819Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
- 2017-07-17T14:58:36.155841Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
- 2017-07-17T14:58:36.156081Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
- 2017-07-17T14:58:36.164568Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
- 2017-07-17T14:58:36.165791Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
- 2017-07-17T14:58:36.165807Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
- 2017-07-17T14:58:36.166124Z 0 [Note] InnoDB: Waiting for purge to start
- 2017-07-17T14:58:36.221277Z 0 [Note] InnoDB: 5.7.18 started; log sequence number 212320189
- 2017-07-17T14:58:36.222226Z 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/var/mysql/ib_buffer_pool
- 2017-07-17T14:58:36.222978Z 0 [Note] Plugin 'FEDERATED' is disabled.
- 2017-07-17T14:58:36.227312Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
- 2017-07-17T14:58:36.227339Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
- 2017-07-17 16:58:36 0x700005970000 InnoDB: Assertion failure in thread 123145396092928 in file fil0fil.cc line 896
- InnoDB: Failing assertion: success
- 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.7/en/forcing-innodb-recovery.html
- InnoDB: about forcing recovery.
- 14:58:36 UTC - mysqld got signal 6 ;
- This could be because you hit a bug. It is also possible that this binary
- or one of the libraries it was linked against is corrupt, improperly built,
- or misconfigured. This error can also be caused by malfunctioning hardware.
- Attempting to collect some information that could help diagnose the problem.
- As this is a crash and something is definitely wrong, the information
- collection process might fail.
- key_buffer_size=8388608
- read_buffer_size=131072
- max_used_connections=0
- max_threads=151
- thread_count=0
- connection_count=0
- It is possible that mysqld could use up to
- key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68215 K bytes of memory
- Hope that's ok; if not, decrease some variables in the equation.
- Thread pointer: 0x0
- Attempting backtrace. You can use the following information to find out
- where mysqld died. If you see no messages after this, something went
- terribly wrong...
- stack_bottom = 0 thread_stack 0x40000
- 0 mysqld 0x000000010e7c0a1a my_print_stacktrace + 58
- 1 mysqld 0x000000010e742c17 handle_fatal_signal + 700
- 2 libsystem_platform.dylib 0x00007fffa7a4fb3a _sigtramp + 26
- 3 libsystem_c.dylib 0x00007fffb073ea20 __stderrp + 0
- 4 libsystem_c.dylib 0x00007fffa78d4420 abort + 129
- 5 mysqld 0x000000010e99ae45 _Z23ut_dbg_assertion_failedPKcS0_m + 161
- 6 mysqld 0x000000010e85196c _ZL18fil_node_open_fileP10fil_node_t + 3573
- 7 mysqld 0x000000010e85a5b8 _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
- 8 mysqld 0x000000010e85ac73 _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 816
- 9 mysqld 0x000000010e824544 _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 384
- 10 mysqld 0x000000010e82478c _Z24buf_read_page_backgroundRK9page_id_tRK11page_size_tb + 46
- 11 mysqld 0x000000010e81ad05 _ZL8buf_loadv + 1458
- 12 mysqld 0x000000010e81a3b9 buf_dump_thread + 134
- 13 libsystem_pthread.dylib 0x00007fffa7a5993b _pthread_body + 180
- 14 libsystem_pthread.dylib 0x00007fffa7a59887 _pthread_body + 0
- 15 libsystem_pthread.dylib 0x00007fffa7a5908d thread_start + 13
- 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.
- ➜ ~
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement