mysql 5.7.23 can not start in docker container

Created on 28 Sep 2018  路  3Comments  路  Source: docker-library/mysql

This my docker-compose:

version: '3'
services:
  author_db:
    image: mysql:5.7.23
    restart: always
    ports:
      - "3306:3306"
    environment:
      MYSQL_ROOT_PASSWORD: developer
      MYSQL_USER: admin_db
      MYSQL_PASSWORD: developer
    volumes:
      - ./tmp/db:/var/lib/mysql
  author_service:
    build: .
    container_name: author_service
    image: author_service:1.0
    command: bundle exec rails s -p 3000 -b '0.0.0.0'
    volumes:
      - .:/author
    ports:
      - "3000:3000"
    depends_on:
      - author_db
    tty: true
    stdin_open: true

Run start :


$sudo docker-compose up 

Creating network "compose_default" with the default driver
Creating compose_author_db_1 ... done
Creating author_service      ... done
Attaching to compose_author_db_1, author_service
author_db_1       | 2018-09-28T08:17:54.142648Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:54.144000Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:54.146997Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:54.147028Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:54.147033Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:54.147036Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:54.147039Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:54.147043Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:54.147260Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:54.147360Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:54.148846Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:54.155756Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:54.157206Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:54.168451Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:54 0x7f5c9a09f740  InnoDB: Assertion failure in thread 140035698063168 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:54 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x561f521d0a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x561f51afc709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f5c99c7d0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f5c98409fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5c9840b42a]
author_db_1       | mysqld(+0x628c7b)[0x561f51ad2c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x561f523a007d]
author_db_1       | mysqld(+0xfa2db1)[0x561f5244cdb1]
author_db_1       | mysqld(+0xfa33e8)[0x561f5244d3e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x561f52456510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x561f5240b64e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x561f523da89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x561f5237e213]
author_db_1       | mysqld(+0x627def)[0x561f51ad1def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x561f5234b0cd]
author_db_1       | mysqld(+0xd6d933)[0x561f52217933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x561f51b473df]
author_db_1       | mysqld(+0xb143d6)[0x561f51fbe3d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x561f51fc15c0]
author_db_1       | mysqld(+0x64ae16)[0x561f51af4e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x561f51af69d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f5c983f72e1]
author_db_1       | mysqld(_start+0x2a)[0x561f51aed0ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_service    | => Booting Puma
author_service    | => Rails 5.2.1 application starting in development 
author_service    | => Run `rails server -h` for more startup options
author_service    | Puma starting in single mode...
author_service    | * Version 3.12.0 (ruby 2.5.1-p57), codename: Llamas in Pajamas
author_service    | * Min threads: 5, max threads: 5
author_service    | * Environment: development
author_service    | * Listening on tcp://0.0.0.0:3000
author_service    | Use Ctrl-C to stop
compose_author_db_1 exited with code 2
author_db_1       | 2018-09-28T08:17:54.142648Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:54.144000Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:54.146997Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:54.147028Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:54.147033Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:54.147036Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:54.147039Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:54.147043Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:54.147260Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:54.147360Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:54.148846Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:54.155756Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:54.157206Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:54.168451Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:54 0x7f5c9a09f740  InnoDB: Assertion failure in thread 140035698063168 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:54 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x561f521d0a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x561f51afc709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f5c99c7d0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f5c98409fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5c9840b42a]
author_db_1       | mysqld(+0x628c7b)[0x561f51ad2c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x561f523a007d]
author_db_1       | mysqld(+0xfa2db1)[0x561f5244cdb1]
author_db_1       | mysqld(+0xfa33e8)[0x561f5244d3e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x561f52456510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x561f5240b64e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x561f523da89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x561f5237e213]
author_db_1       | mysqld(+0x627def)[0x561f51ad1def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x561f5234b0cd]
author_db_1       | mysqld(+0xd6d933)[0x561f52217933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x561f51b473df]
author_db_1       | mysqld(+0xb143d6)[0x561f51fbe3d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x561f51fc15c0]
author_db_1       | mysqld(+0x64ae16)[0x561f51af4e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x561f51af69d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f5c983f72e1]
author_db_1       | mysqld(_start+0x2a)[0x561f51aed0ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:17:56.829002Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:56.830317Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:56.832844Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:56.832863Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:56.832866Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:56.832869Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:56.832872Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:56.832875Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:56.833050Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:56.833126Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:56.834303Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:56.840171Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:56.841621Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:56.853177Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:56 0x7fe8ec522740  InnoDB: Assertion failure in thread 140638373947200 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:56 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x5634b4050a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x5634b397c709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fe8ec1000c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fe8ea88cfff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fe8ea88e42a]
author_db_1       | mysqld(+0x628c7b)[0x5634b3952c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x5634b422007d]
author_db_1       | mysqld(+0xfa2db1)[0x5634b42ccdb1]
author_db_1       | mysqld(+0xfa33e8)[0x5634b42cd3e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5634b42d6510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x5634b428b64e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5634b425a89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5634b41fe213]
author_db_1       | mysqld(+0x627def)[0x5634b3951def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5634b41cb0cd]
author_db_1       | mysqld(+0xd6d933)[0x5634b4097933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x5634b39c73df]
author_db_1       | mysqld(+0xb143d6)[0x5634b3e3e3d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5634b3e415c0]
author_db_1       | mysqld(+0x64ae16)[0x5634b3974e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x5634b39769d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fe8ea87a2e1]
author_db_1       | mysqld(_start+0x2a)[0x5634b396d0ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:17:58.457117Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:58.458662Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:58.461994Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:58.462020Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:58.462026Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:58.462032Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:58.462037Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:58.462043Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:58.462290Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:58.462369Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:58.463569Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:58.469137Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:58.470603Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:58.482129Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:58 0x7f4544f0e740  InnoDB: Assertion failure in thread 139935486109504 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:58 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x55fb5fb25a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x55fb5f451709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f4544aec0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f4543278fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f454327a42a]
author_db_1       | mysqld(+0x628c7b)[0x55fb5f427c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55fb5fcf507d]
author_db_1       | mysqld(+0xfa2db1)[0x55fb5fda1db1]
author_db_1       | mysqld(+0xfa33e8)[0x55fb5fda23e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x55fb5fdab510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55fb5fd6064e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55fb5fd2f89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55fb5fcd3213]
author_db_1       | mysqld(+0x627def)[0x55fb5f426def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55fb5fca00cd]
author_db_1       | mysqld(+0xd6d933)[0x55fb5fb6c933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55fb5f49c3df]
author_db_1       | mysqld(+0xb143d6)[0x55fb5f9133d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55fb5f9165c0]
author_db_1       | mysqld(+0x64ae16)[0x55fb5f449e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55fb5f44b9d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f45432662e1]
author_db_1       | mysqld(_start+0x2a)[0x55fb5f4420ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
compose_author_db_1 exited with code 2
author_db_1       | 2018-09-28T08:17:54.142648Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:54.144000Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:54.146997Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:54.147028Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:54.147033Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:54.147036Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:54.147039Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:54.147043Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:54.147260Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:54.147360Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:54.148846Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:54.155756Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:54.157206Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:54.168451Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:54 0x7f5c9a09f740  InnoDB: Assertion failure in thread 140035698063168 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:54 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x561f521d0a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x561f51afc709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f5c99c7d0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f5c98409fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5c9840b42a]
author_db_1       | mysqld(+0x628c7b)[0x561f51ad2c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x561f523a007d]
author_db_1       | mysqld(+0xfa2db1)[0x561f5244cdb1]
author_db_1       | mysqld(+0xfa33e8)[0x561f5244d3e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x561f52456510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x561f5240b64e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x561f523da89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x561f5237e213]
author_db_1       | mysqld(+0x627def)[0x561f51ad1def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x561f5234b0cd]
author_db_1       | mysqld(+0xd6d933)[0x561f52217933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x561f51b473df]
author_db_1       | mysqld(+0xb143d6)[0x561f51fbe3d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x561f51fc15c0]
author_db_1       | mysqld(+0x64ae16)[0x561f51af4e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x561f51af69d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f5c983f72e1]
author_db_1       | mysqld(_start+0x2a)[0x561f51aed0ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:17:56.829002Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:56.830317Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:56.832844Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:56.832863Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:56.832866Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:56.832869Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:56.832872Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:56.832875Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:56.833050Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:56.833126Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:56.834303Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:56.840171Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:56.841621Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:56.853177Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:56 0x7fe8ec522740  InnoDB: Assertion failure in thread 140638373947200 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:56 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x5634b4050a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x5634b397c709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fe8ec1000c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fe8ea88cfff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fe8ea88e42a]
author_db_1       | mysqld(+0x628c7b)[0x5634b3952c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x5634b422007d]
author_db_1       | mysqld(+0xfa2db1)[0x5634b42ccdb1]
author_db_1       | mysqld(+0xfa33e8)[0x5634b42cd3e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5634b42d6510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x5634b428b64e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x5634b425a89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5634b41fe213]
author_db_1       | mysqld(+0x627def)[0x5634b3951def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5634b41cb0cd]
author_db_1       | mysqld(+0xd6d933)[0x5634b4097933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x5634b39c73df]
author_db_1       | mysqld(+0xb143d6)[0x5634b3e3e3d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5634b3e415c0]
author_db_1       | mysqld(+0x64ae16)[0x5634b3974e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x5634b39769d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fe8ea87a2e1]
author_db_1       | mysqld(_start+0x2a)[0x5634b396d0ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:17:58.457117Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:17:58.458662Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:17:58.461994Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:17:58.462020Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:17:58.462026Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:17:58.462032Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:17:58.462037Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:17:58.462043Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:17:58.462290Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:17:58.462369Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:17:58.463569Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:17:58.469137Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:17:58.470603Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:17:58.482129Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:17:58 0x7f4544f0e740  InnoDB: Assertion failure in thread 139935486109504 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:17:58 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x55fb5fb25a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x55fb5f451709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f4544aec0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f4543278fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f454327a42a]
author_db_1       | mysqld(+0x628c7b)[0x55fb5f427c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55fb5fcf507d]
author_db_1       | mysqld(+0xfa2db1)[0x55fb5fda1db1]
author_db_1       | mysqld(+0xfa33e8)[0x55fb5fda23e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x55fb5fdab510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55fb5fd6064e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55fb5fd2f89a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55fb5fcd3213]
author_db_1       | mysqld(+0x627def)[0x55fb5f426def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55fb5fca00cd]
author_db_1       | mysqld(+0xd6d933)[0x55fb5fb6c933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55fb5f49c3df]
author_db_1       | mysqld(+0xb143d6)[0x55fb5f9133d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55fb5f9165c0]
author_db_1       | mysqld(+0x64ae16)[0x55fb5f449e16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55fb5f44b9d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f45432662e1]
author_db_1       | mysqld(_start+0x2a)[0x55fb5f4420ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:18:00.158338Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:18:00.159627Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:18:00.162386Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:18:00.162406Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:18:00.162411Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:18:00.162416Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:18:00.162421Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:18:00.162424Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:18:00.162604Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:18:00.162687Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:18:00.163852Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:18:00.169344Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:18:00.170871Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:18:00.182563Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:18:00 0x7f116245a740  InnoDB: Assertion failure in thread 139712639903552 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:18:00 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x5567139c9a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x5567132f5709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f11620380c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f11607c4fff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f11607c642a]
author_db_1       | mysqld(+0x628c7b)[0x5567132cbc7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x556713b9907d]
author_db_1       | mysqld(+0xfa2db1)[0x556713c45db1]
author_db_1       | mysqld(+0xfa33e8)[0x556713c463e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x556713c4f510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x556713c0464e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x556713bd389a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x556713b77213]
author_db_1       | mysqld(+0x627def)[0x5567132cadef]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x556713b440cd]
author_db_1       | mysqld(+0xd6d933)[0x556713a10933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x5567133403df]
author_db_1       | mysqld(+0xb143d6)[0x5567137b73d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5567137ba5c0]
author_db_1       | mysqld(+0x64ae16)[0x5567132ede16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x5567132ef9d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f11607b22e1]
author_db_1       | mysqld(_start+0x2a)[0x5567132e60ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
author_db_1       | 2018-09-28T08:18:02.233607Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
author_db_1       | 2018-09-28T08:18:02.234859Z 0 [Note] mysqld (mysqld 5.7.23) starting as process 1 ...
author_db_1       | 2018-09-28T08:18:02.237801Z 0 [Note] InnoDB: PUNCH HOLE support available
author_db_1       | 2018-09-28T08:18:02.237823Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
author_db_1       | 2018-09-28T08:18:02.237827Z 0 [Note] InnoDB: Uses event mutexes
author_db_1       | 2018-09-28T08:18:02.237831Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
author_db_1       | 2018-09-28T08:18:02.237834Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
author_db_1       | 2018-09-28T08:18:02.237836Z 0 [Note] InnoDB: Using Linux native AIO
author_db_1       | 2018-09-28T08:18:02.238027Z 0 [Note] InnoDB: Number of pools: 1
author_db_1       | 2018-09-28T08:18:02.238111Z 0 [Note] InnoDB: Using CPU crc32 instructions
author_db_1       | 2018-09-28T08:18:02.239375Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
author_db_1       | 2018-09-28T08:18:02.246476Z 0 [Note] InnoDB: Completed initialization of buffer pool
author_db_1       | 2018-09-28T08:18:02.248051Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
author_db_1       | 2018-09-28T08:18:02.259374Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
author_db_1       | 2018-09-28 08:18:02 0x7fa7f6141740  InnoDB: Assertion failure in thread 140359364777792 in file ut0ut.cc line 942
author_db_1       | InnoDB: We intentionally generate a memory trap.
author_db_1       | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
author_db_1       | InnoDB: If you get repeated assertion failures or crashes, even
author_db_1       | InnoDB: immediately after the mysqld startup, there may be
author_db_1       | InnoDB: corruption in the InnoDB tablespace. Please refer to
author_db_1       | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
author_db_1       | InnoDB: about forcing recovery.
author_db_1       | 08:18:02 UTC - mysqld got signal 6 ;
author_db_1       | This could be because you hit a bug. It is also possible that this binary
author_db_1       | or one of the libraries it was linked against is corrupt, improperly built,
author_db_1       | or misconfigured. This error can also be caused by malfunctioning hardware.
author_db_1       | Attempting to collect some information that could help diagnose the problem.
author_db_1       | As this is a crash and something is definitely wrong, the information
author_db_1       | collection process might fail.
author_db_1       | 
author_db_1       | key_buffer_size=8388608
author_db_1       | read_buffer_size=131072
author_db_1       | max_used_connections=0
author_db_1       | max_threads=151
author_db_1       | thread_count=0
author_db_1       | connection_count=0
author_db_1       | It is possible that mysqld could use up to 
author_db_1       | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68195 K  bytes of memory
author_db_1       | Hope that's ok; if not, decrease some variables in the equation.
author_db_1       | 
author_db_1       | Thread pointer: 0x0
author_db_1       | Attempting backtrace. You can use the following information to find out
author_db_1       | where mysqld died. If you see no messages after this, something went
author_db_1       | terribly wrong...
author_db_1       | stack_bottom = 0 thread_stack 0x40000
author_db_1       | mysqld(my_print_stacktrace+0x2c)[0x560099447a6c]
author_db_1       | mysqld(handle_fatal_signal+0x479)[0x560098d73709]
author_db_1       | /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fa7f5d1f0c0]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7fa7f44abfff]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fa7f44ad42a]
author_db_1       | mysqld(+0x628c7b)[0x560098d49c7b]
author_db_1       | mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x56009961707d]
author_db_1       | mysqld(+0xfa2db1)[0x5600996c3db1]
author_db_1       | mysqld(+0xfa33e8)[0x5600996c43e8]
author_db_1       | mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x5600996cd510]
author_db_1       | mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x56009968264e]
author_db_1       | mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x56009965189a]
author_db_1       | mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x5600995f5213]
author_db_1       | mysqld(+0x627def)[0x560098d48def]
author_db_1       | mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x5600995c20cd]
author_db_1       | mysqld(+0xd6d933)[0x56009948e933]
author_db_1       | mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x560098dbe3df]
author_db_1       | mysqld(+0xb143d6)[0x5600992353d6]
author_db_1       | mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x5600992385c0]
author_db_1       | mysqld(+0x64ae16)[0x560098d6be16]
author_db_1       | mysqld(_Z11mysqld_mainiPPc+0xc71)[0x560098d6d9d1]
author_db_1       | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fa7f44992e1]
author_db_1       | mysqld(_start+0x2a)[0x560098d640ba]
author_db_1       | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
author_db_1       | information that should help you find out what is causing the crash.
compose_author_db_1 exited with code 2

question
Source
picture EnziinSystem

Most helpful comment

https://github.com/docker-library/mysql/issues/361#issuecomment-356744484

  1. docker-compose down
  2. Deleted old volumes (if there is no significant data) docker system prune --force --volumes
  3. Added command: --disable-partition-engine-check to mysql section in docker-compose.yml
  4. Ran it with docker-compose up -d to set it up in background.

If that doesn't work could you post the output of docker info

picture wglambert on 28 Sep 2018
👍9 🚀3 ❤3 🎉3

All 3 comments

https://github.com/docker-library/mysql/issues/361#issuecomment-356744484

  1. docker-compose down
  2. Deleted old volumes (if there is no significant data) docker system prune --force --volumes
  3. Added command: --disable-partition-engine-check to mysql section in docker-compose.yml
  4. Ran it with docker-compose up -d to set it up in background.

If that doesn't work could you post the output of docker info

wglambert picture wglambert on 28 Sep 2018
👍9 🚀3 ❤3 🎉3

i'm going to close as there doesn't seem to be anything denoting an error in the image.

You could also try asking the Docker Community Forums, the Docker Community Slack, or Stack Overflow. As these repositories are for issues with the image and not necessarily for questions of usability

wglambert picture wglambert on 4 Oct 2018

I had similar error with:

  mysql-jira:
    image: mysql:5.7
    environment:
      MYSQL_ROOT_PASSWORD: root
    ports:
      - 3306:3306

Basically I've downgraded from the latest tag to 5.7, so most likely the old volumes did mess something up.

The suggested steps helped (downing the service and pruning the old volumes), thanks.

kenorb picture kenorb on 17 Jul 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

UpCoder picture UpCoder  路  3Comments
TheNotary picture TheNotary  路  4Comments
kjaltana picture kjaltana  路  3Comments
tomnewport picture tomnewport  路  3Comments
bscheshirwork picture bscheshirwork  路  5Comments