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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f0fdc0009a8 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 = 0x7f0ff3ffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x556a0a7bcbae] mysqld(handle_fatal_signal+0x345)[0x556a0a23a795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f10638e8890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f1061c72067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f1061c73448] mysqld(+0x42330e)[0x556a09fd430e] mysqld(+0x9925b8)[0x556a0a5435b8] mysqld(+0x99da39)[0x556a0a54ea39] mysqld(+0x9a0e03)[0x556a0a551e03] mysqld(+0x8f7915)[0x556a0a4a8915] mysqld(+0x8f8fe9)[0x556a0a4a9fe9] mysqld(+0x8b6848)[0x556a0a467848] mysqld(+0x926ef6)[0x556a0a4d7ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f10638e1064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f1061d2562d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:28:58 140379750442880 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Uses event mutexes 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Number of pools: 1 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:28:58 140378360882944 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:28:58 140379750442880 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:28:59 140379750442880 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:28:59 140377650624256 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:28:59 140379750442880 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:28:59 140379750442880 [Note] Recovering after a crash using master2-bin 2018-08-28 9:28:59 140379750442880 [Note] Starting crash recovery... 2018-08-28 9:28:59 140379750442880 [Note] Crash recovery finished. 2018-08-28 9:28:59 140379750442880 [Note] Server socket created on IP: '::'. 2018-08-28 9:28:59 140379750442880 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:28:59 140379750442880 [Note] Reading of all Master_info entries succeded 2018-08-28 9:28:59 140379750442880 [Note] Added new Master_info '' to hash table 2018-08-28 9:28:59 140379750442880 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:28:59 0x7fac497fa700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fac280009a8 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 = 0x7fac497f9dc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55b5f48a9bae] mysqld(handle_fatal_signal+0x345)[0x55b5f4327795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7facb4e6b890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7facb31f5067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7facb31f6448] mysqld(+0x42330e)[0x55b5f40c130e] mysqld(+0x9925b8)[0x55b5f46305b8] mysqld(+0x99da39)[0x55b5f463ba39] mysqld(+0x9a0e03)[0x55b5f463ee03] mysqld(+0x8f7915)[0x55b5f4595915] mysqld(+0x8f8fe9)[0x55b5f4596fe9] mysqld(+0x8b6848)[0x55b5f4554848] mysqld(+0x926ef6)[0x55b5f45c4ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7facb4e64064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7facb32a862d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 3 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:30:00 140454422722432 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Uses event mutexes 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Number of pools: 1 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:30:00 140453031638784 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:30:00 140454422722432 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:30:01 140454422722432 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:30:01 140452468614912 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:30:01 140454422722432 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:30:01 140454422722432 [Note] Recovering after a crash using master2-bin 2018-08-28 9:30:01 140454422722432 [Note] Starting crash recovery... 2018-08-28 9:30:01 140454422722432 [Note] Crash recovery finished. 2018-08-28 9:30:01 140454422722432 [Note] Server socket created on IP: '::'. 2018-08-28 9:30:01 140454422722432 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:30:01 140454422722432 [Note] Reading of all Master_info entries succeded 2018-08-28 9:30:01 140454422722432 [Note] Added new Master_info '' to hash table 2018-08-28 9:30:01 140454422722432 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:30:01 0x7fbda3fff700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:30: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fbd8c0009a8 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 = 0x7fbda3ffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55ff1d847bae] mysqld(handle_fatal_signal+0x345)[0x55ff1d2c5795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fbe17b74890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fbe15efe067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fbe15eff448] mysqld(+0x42330e)[0x55ff1d05f30e] mysqld(+0x9925b8)[0x55ff1d5ce5b8] mysqld(+0x99da39)[0x55ff1d5d9a39] mysqld(+0x9a0e03)[0x55ff1d5dce03] mysqld(+0x8f7915)[0x55ff1d533915] mysqld(+0x8f8fe9)[0x55ff1d534fe9] mysqld(+0x8b6848)[0x55ff1d4f2848] mysqld(+0x926ef6)[0x55ff1d562ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fbe17b6d064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbe15fb162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:31:02 140602619127680 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Uses event mutexes 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Number of pools: 1 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:31:02 140601229420288 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:31:02 140602619127680 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:31:03 140602619127680 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:31:03 140600317835008 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:31:03 140602619127680 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:31:03 140602619127680 [Note] Recovering after a crash using master2-bin 2018-08-28 9:31:03 140602619127680 [Note] Starting crash recovery... 2018-08-28 9:31:03 140602619127680 [Note] Crash recovery finished. 2018-08-28 9:31:03 140602619127680 [Note] Server socket created on IP: '::'. 2018-08-28 9:31:03 140602619127680 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:31:03 140602619127680 [Note] Reading of all Master_info entries succeded 2018-08-28 9:31:03 140602619127680 [Note] Added new Master_info '' to hash table 2018-08-28 9:31:03 140602619127680 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:31:03 0x7fe02dffb700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:31: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fe0180009a8 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 = 0x7fe02dffadc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55d825644bae] mysqld(handle_fatal_signal+0x345)[0x55d8250c2795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fe098e8f890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fe097219067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fe09721a448] mysqld(+0x42330e)[0x55d824e5c30e] mysqld(+0x9925b8)[0x55d8253cb5b8] mysqld(+0x99da39)[0x55d8253d6a39] mysqld(+0x9a0e03)[0x55d8253d9e03] mysqld(+0x8f7915)[0x55d825330915] mysqld(+0x8f8fe9)[0x55d825331fe9] mysqld(+0x8b6848)[0x55d8252ef848] mysqld(+0x926ef6)[0x55d82535fef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fe098e88064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fe0972cc62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:32:05 139652998260608 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Uses event mutexes 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Number of pools: 1 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:32:05 139651609192192 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:32:05 139652998260608 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:32:05 139650970666752 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:32:05 139652998260608 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:32:05 139652998260608 [Note] Recovering after a crash using master2-bin 2018-08-28 9:32:05 139652998260608 [Note] Starting crash recovery... 2018-08-28 9:32:05 139652998260608 [Note] Crash recovery finished. 2018-08-28 9:32:05 139652998260608 [Note] Server socket created on IP: '::'. 2018-08-28 9:32:05 139652998260608 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:32:05 139652998260608 [Note] Reading of all Master_info entries succeded 2018-08-28 9:32:05 139652998260608 [Note] Added new Master_info '' to hash table 2018-08-28 9:32:05 139652998260608 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:32:06 0x7f03077fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:32: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f02fc0009a8 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 = 0x7f03077fddc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x559f1e79ebae] mysqld(handle_fatal_signal+0x345)[0x559f1e21c795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f037f187890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f037d511067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f037d512448] mysqld(+0x42330e)[0x559f1dfb630e] mysqld(+0x9925b8)[0x559f1e5255b8] mysqld(+0x99da39)[0x559f1e530a39] mysqld(+0x9a0e03)[0x559f1e533e03] mysqld(+0x8f7915)[0x559f1e48a915] mysqld(+0x8f8fe9)[0x559f1e48bfe9] mysqld(+0x8b6848)[0x559f1e449848] mysqld(+0x926ef6)[0x559f1e4b9ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f037f180064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f037d5c462d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 3 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:33:07 140330352052096 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Uses event mutexes 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Number of pools: 1 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:33:07 140328962983680 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:33:07 140330352052096 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:33:08 140330352052096 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:33:08 140328182998784 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:33:08 140330352052096 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:33:08 140330352052096 [Note] Recovering after a crash using master2-bin 2018-08-28 9:33:08 140330352052096 [Note] Starting crash recovery... 2018-08-28 9:33:08 140330352052096 [Note] Crash recovery finished. 2018-08-28 9:33:08 140330352052096 [Note] Server socket created on IP: '::'. 2018-08-28 9:33:08 140330352052096 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:33:08 140330352052096 [Note] Reading of all Master_info entries succeded 2018-08-28 9:33:08 140330352052096 [Note] Added new Master_info '' to hash table 2018-08-28 9:33:08 140330352052096 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:33:08 0x7fa0c8ff9700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:33: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fa0a40009a8 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 = 0x7fa0c8ff8dc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55a7a210abae] mysqld(handle_fatal_signal+0x345)[0x55a7a1b88795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fa134871890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fa132bfb067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa132bfc448] mysqld(+0x42330e)[0x55a7a192230e] mysqld(+0x9925b8)[0x55a7a1e915b8] mysqld(+0x99da39)[0x55a7a1e9ca39] mysqld(+0x9a0e03)[0x55a7a1e9fe03] mysqld(+0x8f7915)[0x55a7a1df6915] mysqld(+0x8f8fe9)[0x55a7a1df7fe9] mysqld(+0x8b6848)[0x55a7a1db5848] mysqld(+0x926ef6)[0x55a7a1e25ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fa13486a064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa132cae62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 4 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:34:10 140307672831872 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Uses event mutexes 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Number of pools: 1 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:34:10 140306283960064 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:34:10 140307672831872 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:34:11 140307672831872 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:34:11 140305709922048 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:34:11 140307672831872 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:34:11 140307672831872 [Note] Recovering after a crash using master2-bin 2018-08-28 9:34:11 140307672831872 [Note] Starting crash recovery... 2018-08-28 9:34:11 140307672831872 [Note] Crash recovery finished. 2018-08-28 9:34:11 140307672831872 [Note] Server socket created on IP: '::'. 2018-08-28 9:34:11 140307672831872 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:34:11 140307672831872 [Note] Reading of all Master_info entries succeded 2018-08-28 9:34:11 140307672831872 [Note] Added new Master_info '' to hash table 2018-08-28 9:34:11 140307672831872 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:34:11 0x7f9b81ffb700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:34:11 [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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f9b6c0009a8 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 = 0x7f9b81ffadc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55b90b166bae] mysqld(handle_fatal_signal+0x345)[0x55b90abe4795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f9becbda890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f9beaf64067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f9beaf65448] mysqld(+0x42330e)[0x55b90a97e30e] mysqld(+0x9925b8)[0x55b90aeed5b8] mysqld(+0x99da39)[0x55b90aef8a39] mysqld(+0x9a0e03)[0x55b90aefbe03] mysqld(+0x8f7915)[0x55b90ae52915] mysqld(+0x8f8fe9)[0x55b90ae53fe9] mysqld(+0x8b6848)[0x55b90ae11848] mysqld(+0x926ef6)[0x55b90ae81ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f9becbd3064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9beb01762d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:35:12 139688106407808 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Uses event mutexes 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Number of pools: 1 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:35:12 139686715520768 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:35:12 139688106407808 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:35:13 139688106407808 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:35:13 139686144104192 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:35:13 139688106407808 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:35:13 139688106407808 [Note] Recovering after a crash using master2-bin 2018-08-28 9:35:13 139688106407808 [Note] Starting crash recovery... 2018-08-28 9:35:13 139688106407808 [Note] Crash recovery finished. 2018-08-28 9:35:13 139688106407808 [Note] Server socket created on IP: '::'. 2018-08-28 9:35:13 139688106407808 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:35:13 139688106407808 [Note] Reading of all Master_info entries succeded 2018-08-28 9:35:13 139688106407808 [Note] Added new Master_info '' to hash table 2018-08-28 9:35:13 139688106407808 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:35:13 0x7f0b377fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:35: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f0b240009a8 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 = 0x7f0b377fddc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55f0c109abae] mysqld(handle_fatal_signal+0x345)[0x55f0c0b18795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0babb44890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0ba9ece067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0ba9ecf448] mysqld(+0x42330e)[0x55f0c08b230e] mysqld(+0x9925b8)[0x55f0c0e215b8] mysqld(+0x99da39)[0x55f0c0e2ca39] mysqld(+0x9a0e03)[0x55f0c0e2fe03] mysqld(+0x8f7915)[0x55f0c0d86915] mysqld(+0x8f8fe9)[0x55f0c0d87fe9] mysqld(+0x8b6848)[0x55f0c0d45848] mysqld(+0x926ef6)[0x55f0c0db5ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0babb3d064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0ba9f8162d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 4 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:36:14 139686380861312 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Uses event mutexes 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Number of pools: 1 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:36:14 139684992100096 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:36:14 139686380861312 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:36:15 139686380861312 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:36:15 139684147623680 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:36:15 139686380861312 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:36:15 139686380861312 [Note] Recovering after a crash using master2-bin 2018-08-28 9:36:15 139686380861312 [Note] Starting crash recovery... 2018-08-28 9:36:15 139686380861312 [Note] Crash recovery finished. 2018-08-28 9:36:15 139686380861312 [Note] Server socket created on IP: '::'. 2018-08-28 9:36:15 139686380861312 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:36:15 139686380861312 [Note] Reading of all Master_info entries succeded 2018-08-28 9:36:15 139686380861312 [Note] Added new Master_info '' to hash table 2018-08-28 9:36:15 139686380861312 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' 2018-08-28 09:36:15 0x7f0ad9ffb700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:36: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f0acc0009a8 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 = 0x7f0ad9ffadc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x559efa75cbae] mysqld(handle_fatal_signal+0x345)[0x559efa1da795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0b44da8890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0b43132067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0b43133448] mysqld(+0x42330e)[0x559ef9f7430e] mysqld(+0x9925b8)[0x559efa4e35b8] mysqld(+0x99da39)[0x559efa4eea39] mysqld(+0x9a0e03)[0x559efa4f1e03] mysqld(+0x8f7915)[0x559efa448915] mysqld(+0x8f8fe9)[0x559efa449fe9] mysqld(+0x8b6848)[0x559efa407848] mysqld(+0x926ef6)[0x559efa477ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0b44da1064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0b431e562d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 1 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:37:17 139982890076032 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Uses event mutexes 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Number of pools: 1 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:37:17 139981500778240 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:37:17 139982890076032 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:37:17 139980936558336 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:37:17 139982890076032 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:37:17 139982890076032 [Note] Recovering after a crash using master2-bin 2018-08-28 9:37:17 139982890076032 [Note] Starting crash recovery... 2018-08-28 9:37:17 139982890076032 [Note] Crash recovery finished. 2018-08-28 9:37:17 139982890076032 [Note] Server socket created on IP: '::'. 2018-08-28 9:37:17 139982890076032 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:37:17 139982890076032 [Note] Reading of all Master_info entries succeded 2018-08-28 09:37:17 0x7f4fdb7fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 2018-08-28 9:37:17 139982890076032 [Note] Added new Master_info '' to hash table 180828 9:37: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f4fd00009a8 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... 2018-08-28 9:37:17 139982890076032 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002407' stack_bottom = 0x7f4fdb7fddc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55fc69e6bbae] mysqld(handle_fatal_signal+0x345)[0x55fc698e9795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f504e2e1890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f504c66b067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f504c66c448] mysqld(+0x42330e)[0x55fc6968330e] mysqld(+0x9925b8)[0x55fc69bf25b8] mysqld(+0x99da39)[0x55fc69bfda39] mysqld(+0x9a0e03)[0x55fc69c00e03] mysqld(+0x8f7915)[0x55fc69b57915] mysqld(+0x8f8fe9)[0x55fc69b58fe9] mysqld(+0x8b6848)[0x55fc69b16848] mysqld(+0x926ef6)[0x55fc69b86ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f504e2da064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f504c71e62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:38:19 140433187907456 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Uses event mutexes 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Number of pools: 1 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:38:19 140431798806272 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:38:19 140433187907456 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:38:20 140433187907456 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:38:20 140431304144640 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:38:20 140433187907456 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:38:20 140433187907456 [Note] Recovering after a crash using master2-bin 2018-08-28 9:38:20 140433187907456 [Note] Starting crash recovery... 2018-08-28 9:38:20 140433187907456 [Note] Crash recovery finished. 2018-08-28 9:38:20 140433187907456 [Note] Server socket created on IP: '::'. 2018-08-28 9:38:20 140433187907456 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:38:20 140433187907456 [Note] Reading of all Master_info entries succeded 2018-08-28 9:38:20 140433187907456 [Note] Added new Master_info '' to hash table 2018-08-28 09:38:20 0x7fb8b6ffd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:38: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fb8a40009a8 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 = 0x7fb8b6ffcdc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55743d7e9bae] mysqld(handle_fatal_signal+0x345)[0x55743d267795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fb92605b890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fb9243e5067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fb9243e6448] mysqld(+0x42330e)[0x55743d00130e] mysqld(+0x9925b8)[0x55743d5705b8] mysqld(+0x99da39)[0x55743d57ba39] mysqld(+0x9a0e03)[0x55743d57ee03] mysqld(+0x8f7915)[0x55743d4d5915] mysqld(+0x8f8fe9)[0x55743d4d6fe9] mysqld(+0x8b6848)[0x55743d494848] mysqld(+0x926ef6)[0x55743d504ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fb926054064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb92449862d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:39:21 140316131895168 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Uses event mutexes 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Number of pools: 1 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:39:21 140314741679872 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:39:21 140316131895168 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:39:22 140316131895168 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:39:23 140316131895168 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:39:23 140314165638912 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:39:23 140316131895168 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:39:23 140316131895168 [Note] Recovering after a crash using master2-bin 2018-08-28 9:39:23 140316131895168 [Note] Starting crash recovery... 2018-08-28 9:39:23 140316131895168 [Note] Crash recovery finished. 2018-08-28 9:39:24 140316131895168 [Note] Server socket created on IP: '::'. 2018-08-28 09:39:24 0x7f9d797fa700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:39: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f9d640009a8 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 = 0x7f9d797f9dc8 thread_stack 0x49000 2018-08-28 9:39:24 140316131895168 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:39:24 140316131895168 [Note] Reading of all Master_info entries succeded 2018-08-28 9:39:24 140316131895168 [Note] Added new Master_info '' to hash table 2018-08-28 9:39:24 140316131895168 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002408' mysqld(my_print_stacktrace+0x2e)[0x557ac1f34bae] mysqld(handle_fatal_signal+0x345)[0x557ac19b2795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f9de4f0b890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f9de3295067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f9de3296448] mysqld(+0x42330e)[0x557ac174c30e] mysqld(+0x9925b8)[0x557ac1cbb5b8] mysqld(+0x99da39)[0x557ac1cc6a39] mysqld(+0x9a0e03)[0x557ac1cc9e03] mysqld(+0x8f7915)[0x557ac1c20915] mysqld(+0x8f8fe9)[0x557ac1c21fe9] mysqld(+0x8b6848)[0x557ac1bdf848] mysqld(+0x926ef6)[0x557ac1c4fef6] 2018-08-28 9:39:24 140316131895168 [Note] mysqld: ready for connections. Version: '10.2.16-MariaDB-10.2.16+maria~jessie-log' socket: '/var/run/mysqld/mysqld.sock' port: 33061 mariadb.org binary distribution 2018-08-28 9:39:24 140315981993728 [Note] Slave SQL thread initialized, starting replication in log 'master1-bin.000723' at position 61962088, relay log './master2-relay-bin.002095' position: 1838743 2018-08-28 9:39:24 140315982296832 [Note] Slave I/O thread: connected to master 'slave@192.168.1.220:33061',replication started in log 'master1-bin.000748' at position 19771350 /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f9de4f04064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9de334862d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:40:25 140090143426432 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Uses event mutexes 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Number of pools: 1 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:40:25 140088747939584 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:40:25 140090143426432 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:40:26 140090143426432 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:40:26 140088184915712 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:40:26 140090143426432 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:40:26 140090143426432 [Note] Recovering after a crash using master2-bin 2018-08-28 9:40:26 140090143426432 [Note] Starting crash recovery... 2018-08-28 9:40:26 140090143426432 [Note] Crash recovery finished. 2018-08-28 9:40:26 140090143426432 [Note] Server socket created on IP: '::'. 2018-08-28 9:40:26 140090143426432 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:40:26 140090143426432 [Note] Reading of all Master_info entries succeded 2018-08-28 9:40:26 140090143426432 [Note] Added new Master_info '' to hash table 2018-08-28 09:40:26 0x7f68d3fff700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:40: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f68c40009a8 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 = 0x7f68d3ffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55cf33e3bbae] mysqld(handle_fatal_signal+0x345)[0x55cf338b9795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f6946fa5890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f694532f067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f6945330448] mysqld(+0x42330e)[0x55cf3365330e] mysqld(+0x9925b8)[0x55cf33bc25b8] mysqld(+0x99da39)[0x55cf33bcda39] mysqld(+0x9a0e03)[0x55cf33bd0e03] mysqld(+0x8f7915)[0x55cf33b27915] mysqld(+0x8f8fe9)[0x55cf33b28fe9] mysqld(+0x8b6848)[0x55cf33ae6848] mysqld(+0x926ef6)[0x55cf33b56ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f6946f9e064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f69453e262d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 1 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:41:27 140189101664128 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Uses event mutexes 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Number of pools: 1 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:41:27 140187709028096 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:41:27 140189101664128 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:41:29 140189101664128 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:41:29 140189101664128 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:41:30 140189101664128 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:41:30 140187279529728 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:41:30 140189101664128 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:41:30 140189101664128 [Note] Recovering after a crash using master2-bin 2018-08-28 9:41:30 140189101664128 [Note] Starting crash recovery... 2018-08-28 9:41:30 140189101664128 [Note] Crash recovery finished. 2018-08-28 9:41:30 140189101664128 [Note] Server socket created on IP: '::'. 2018-08-28 9:41:30 140189101664128 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:41:30 140189101664128 [Note] Reading of all Master_info entries succeded 2018-08-28 9:41:30 140189101664128 [Note] Added new Master_info '' to hash table 2018-08-28 9:41:30 140189101664128 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002409' 2018-08-28 09:41:30 0x7f7fe5ffb700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:41: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7fc80009a8 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 = 0x7f7fe5ffadc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x556c89925bae] mysqld(handle_fatal_signal+0x345)[0x556c893a3795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f8051593890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f804f91d067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f804f91e448] mysqld(+0x42330e)[0x556c8913d30e] mysqld(+0x9925b8)[0x556c896ac5b8] mysqld(+0x99da39)[0x556c896b7a39] mysqld(+0x9a0e03)[0x556c896bae03] mysqld(+0x8f7915)[0x556c89611915] mysqld(+0x8f8fe9)[0x556c89612fe9] mysqld(+0x8b6848)[0x556c895d0848] mysqld(+0x926ef6)[0x556c89640ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f805158c064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f804f9d062d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 3 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:42:32 139778410858368 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Uses event mutexes 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Number of pools: 1 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:42:32 139777021503232 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:42:32 139778410858368 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:42:32 139776455849728 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:42:32 139778410858368 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:42:32 139778410858368 [Note] Recovering after a crash using master2-bin 2018-08-28 9:42:32 139778410858368 [Note] Starting crash recovery... 2018-08-28 9:42:32 139778410858368 [Note] Crash recovery finished. 2018-08-28 9:42:32 139778410858368 [Note] Server socket created on IP: '::'. 2018-08-28 9:42:32 139778410858368 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:42:32 139778410858368 [Note] Reading of all Master_info entries succeded 2018-08-28 9:42:32 139778410858368 [Note] Added new Master_info '' to hash table 2018-08-28 9:42:32 139778410858368 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002409' 2018-08-28 09:42:32 0x7f203effd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:42: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f20280009a8 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 = 0x7f203effcdc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x56492e115bae] mysqld(handle_fatal_signal+0x345)[0x56492db93795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f20b244d890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f20b07d7067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f20b07d8448] mysqld(+0x42330e)[0x56492d92d30e] mysqld(+0x9925b8)[0x56492de9c5b8] mysqld(+0x99da39)[0x56492dea7a39] mysqld(+0x9a0e03)[0x56492deaae03] mysqld(+0x8f7915)[0x56492de01915] mysqld(+0x8f8fe9)[0x56492de02fe9] mysqld(+0x8b6848)[0x56492ddc0848] mysqld(+0x926ef6)[0x56492de30ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f20b2446064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f20b088a62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 3 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:43:34 140261749516160 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Uses event mutexes 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Number of pools: 1 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:43:34 140260353697536 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:43:34 140261749516160 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:43:35 140261749516160 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:43:35 140259849389824 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:43:35 140261749516160 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:43:35 140261749516160 [Note] Recovering after a crash using master2-bin 2018-08-28 9:43:35 140261749516160 [Note] Starting crash recovery... 2018-08-28 9:43:35 140261749516160 [Note] Crash recovery finished. 2018-08-28 9:43:35 140261749516160 [Note] Server socket created on IP: '::'. 2018-08-28 9:43:35 140261749516160 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:43:35 140261749516160 [Note] Reading of all Master_info entries succeded 2018-08-28 9:43:35 140261749516160 [Note] Added new Master_info '' to hash table 2018-08-28 9:43:35 140261749516160 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002409' 2018-08-28 09:43:35 0x7f90cbfff700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:43: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f90b40009a8 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 = 0x7f90cbffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x557c67b10bae] mysqld(handle_fatal_signal+0x345)[0x557c6758e795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f913b7f7890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f9139b81067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f9139b82448] 2018-08-28 9:43:35 140261557298944 [Note] Slave I/O thread: connected to master 'slave@192.168.1.220:33061',replication started in log 'master1-bin.000748' at position 19771350 2018-08-28 9:43:35 140261749516160 [Note] mysqld: ready for connections. Version: '10.2.16-MariaDB-10.2.16+maria~jessie-log' socket: '/var/run/mysqld/mysqld.sock' port: 33061 mariadb.org binary distribution mysqld(+0x42330e)[0x557c6732830e] 2018-08-28 9:43:35 140261556995840 [Note] Slave SQL thread initialized, starting replication in log 'master1-bin.000723' at position 61962088, relay log './master2-relay-bin.002095' position: 1838743 mysqld(+0x9925b8)[0x557c678975b8] mysqld(+0x99da39)[0x557c678a2a39] mysqld(+0x9a0e03)[0x557c678a5e03] mysqld(+0x8f7915)[0x557c677fc915] mysqld(+0x8f8fe9)[0x557c677fdfe9] mysqld(+0x8b6848)[0x557c677bb848] mysqld(+0x926ef6)[0x557c6782bef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f913b7f0064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9139c3462d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:44:36 140579873093504 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Uses event mutexes 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Number of pools: 1 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:44:36 140578483943168 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:44:36 140579873093504 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:44:37 140579873093504 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:44:37 140577635038976 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:44:37 140579873093504 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:44:37 140579873093504 [Note] Recovering after a crash using master2-bin 2018-08-28 9:44:37 140579873093504 [Note] Starting crash recovery... 2018-08-28 9:44:37 140579873093504 [Note] Crash recovery finished. 2018-08-28 9:44:37 140579873093504 [Note] Server socket created on IP: '::'. 2018-08-28 9:44:37 140579873093504 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:44:37 140579873093504 [Note] Reading of all Master_info entries succeded 2018-08-28 9:44:37 140579873093504 [Note] Added new Master_info '' to hash table 2018-08-28 09:44:37 0x7fdae17fa700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:44:37 [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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fdacc0009a8 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 = 0x7fdae17f9dc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55d1fae49bae] mysqld(handle_fatal_signal+0x345)[0x55d1fa8c7795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fdb4d240890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fdb4b5ca067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fdb4b5cb448] mysqld(+0x42330e)[0x55d1fa66130e] mysqld(+0x9925b8)[0x55d1fabd05b8] mysqld(+0x99da39)[0x55d1fabdba39] mysqld(+0x9a0e03)[0x55d1fabdee03] mysqld(+0x8f7915)[0x55d1fab35915] mysqld(+0x8f8fe9)[0x55d1fab36fe9] mysqld(+0x8b6848)[0x55d1faaf4848] mysqld(+0x926ef6)[0x55d1fab64ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fdb4d239064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fdb4b67d62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 1 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:45:38 140105100199808 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Uses event mutexes 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Number of pools: 1 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:45:38 140103711213312 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:45:38 140105100199808 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:45:39 140105100199808 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:45:39 140103150192384 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:45:39 140105100199808 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:45:39 140105100199808 [Note] Recovering after a crash using master2-bin 2018-08-28 9:45:39 140105100199808 [Note] Starting crash recovery... 2018-08-28 9:45:39 140105100199808 [Note] Crash recovery finished. 2018-08-28 9:45:39 140105100199808 [Note] Server socket created on IP: '::'. 2018-08-28 9:45:39 140105100199808 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 09:45:39 0x7f6c46ffd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:45: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f6c340009a8 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 = 0x7f6c46ffcdc8 thread_stack 0x49000 2018-08-28 9:45:39 140105100199808 [Note] Reading of all Master_info entries succeded 2018-08-28 9:45:39 140105100199808 [Note] Added new Master_info '' to hash table 2018-08-28 9:45:39 140105100199808 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002410' mysqld(my_print_stacktrace+0x2e)[0x555e8e320bae] mysqld(handle_fatal_signal+0x345)[0x555e8dd9e795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f6cc2789890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f6cc0b13067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f6cc0b14448] mysqld(+0x42330e)[0x555e8db3830e] mysqld(+0x9925b8)[0x555e8e0a75b8] mysqld(+0x99da39)[0x555e8e0b2a39] mysqld(+0x9a0e03)[0x555e8e0b5e03] mysqld(+0x8f7915)[0x555e8e00c915] mysqld(+0x8f8fe9)[0x555e8e00dfe9] mysqld(+0x8b6848)[0x555e8dfcb848] mysqld(+0x926ef6)[0x555e8e03bef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f6cc2782064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6cc0bc662d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:46:41 139668508043136 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Uses event mutexes 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Number of pools: 1 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:46:41 139667111339776 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:46:41 139668508043136 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:46:41 139666472814336 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:46:41 139668508043136 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:46:41 139668508043136 [Note] Recovering after a crash using master2-bin 2018-08-28 9:46:41 139668508043136 [Note] Starting crash recovery... 2018-08-28 9:46:41 139668508043136 [Note] Crash recovery finished. 2018-08-28 9:46:42 139668508043136 [Note] Server socket created on IP: '::'. 2018-08-28 9:46:42 139668508043136 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:46:42 139668508043136 [Note] Reading of all Master_info entries succeded 2018-08-28 9:46:42 139668508043136 [Note] Added new Master_info '' to hash table 2018-08-28 9:46:42 139668508043136 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002410' 2018-08-28 09:46:42 0x7f06a3fff700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:46:42 [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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f06940009a8 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 = 0x7f06a3ffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55e0debc3bae] mysqld(handle_fatal_signal+0x345)[0x55e0de641795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f071b8cf890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0719c59067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0719c5a448] mysqld(+0x42330e)[0x55e0de3db30e] mysqld(+0x9925b8)[0x55e0de94a5b8] mysqld(+0x99da39)[0x55e0de955a39] mysqld(+0x9a0e03)[0x55e0de958e03] mysqld(+0x8f7915)[0x55e0de8af915] mysqld(+0x8f8fe9)[0x55e0de8b0fe9] mysqld(+0x8b6848)[0x55e0de86e848] mysqld(+0x926ef6)[0x55e0de8deef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f071b8c8064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0719d0c62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:47:43 139646898734976 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Uses event mutexes 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Number of pools: 1 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:47:43 139645502285568 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:47:43 139646898734976 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:47:44 139646898734976 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:47:44 139645266413312 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:47:44 139646898734976 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:47:44 139646898734976 [Note] Recovering after a crash using master2-bin 2018-08-28 9:47:44 139646898734976 [Note] Starting crash recovery... 2018-08-28 9:47:44 139646898734976 [Note] Crash recovery finished. 2018-08-28 09:47:44 0x7f01b2ffd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:47: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f01840009a8 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 = 0x7f01b2ffcdc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55bc9756ebae] mysqld(handle_fatal_signal+0x345)[0x55bc96fec795] 2018-08-28 9:47:44 139646898734976 [Note] Server socket created on IP: '::'. /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0213891890] 2018-08-28 9:47:44 139646898734976 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0211c1b067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0211c1c448] 2018-08-28 9:47:44 139646898734976 [Note] Reading of all Master_info entries succeded 2018-08-28 9:47:44 139646898734976 [Note] Added new Master_info '' to hash table 2018-08-28 9:47:44 139646898734976 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002410' mysqld(+0x42330e)[0x55bc96d8630e] mysqld(+0x9925b8)[0x55bc972f55b8] mysqld(+0x99da39)[0x55bc97300a39] mysqld(+0x9a0e03)[0x55bc97303e03] mysqld(+0x8f7915)[0x55bc9725a915] mysqld(+0x8f8fe9)[0x55bc9725bfe9] mysqld(+0x8b6848)[0x55bc97219848] mysqld(+0x926ef6)[0x55bc97289ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f021388a064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0211cce62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 4 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:48:45 140444087527296 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Uses event mutexes 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Number of pools: 1 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:48:45 140442696873728 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:48:45 140444087527296 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:48:46 140444087527296 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:48:46 140442184173312 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:48:46 140444087527296 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:48:46 140444087527296 [Note] Recovering after a crash using master2-bin 2018-08-28 9:48:46 140444087527296 [Note] Starting crash recovery... 2018-08-28 9:48:46 140444087527296 [Note] Crash recovery finished. 2018-08-28 9:48:46 140444087527296 [Note] Server socket created on IP: '::'. 2018-08-28 9:48:46 140444087527296 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:48:46 140444087527296 [Note] Reading of all Master_info entries succeded 2018-08-28 9:48:46 140444087527296 [Note] Added new Master_info '' to hash table 2018-08-28 9:48:46 140444087527296 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002410' 2018-08-28 09:48:46 0x7fbb3ffff700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:48: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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fbb280009a8 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 = 0x7fbb3fffedc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x55b0d354ebae] mysqld(handle_fatal_signal+0x345)[0x55b0d2fcc795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fbbafb0b890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fbbade95067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fbbade96448] mysqld(+0x42330e)[0x55b0d2d6630e] mysqld(+0x9925b8)[0x55b0d32d55b8] mysqld(+0x99da39)[0x55b0d32e0a39] mysqld(+0x9a0e03)[0x55b0d32e3e03] mysqld(+0x8f7915)[0x55b0d323a915] mysqld(+0x8f8fe9)[0x55b0d323bfe9] mysqld(+0x8b6848)[0x55b0d31f9848] mysqld(+0x926ef6)[0x55b0d3269ef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fbbafb04064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbbadf4862d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing 2018-08-28 9:49:47 140103925024640 [Note] mysqld (mysqld 10.2.16-MariaDB-10.2.16+maria~jessie-log) starting as process 1 ... 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Uses event mutexes 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Compressed tables use zlib 1.2.8 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Using Linux native AIO 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Number of pools: 1 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Using SSE2 crc32 instructions 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Completed initialization of buffer pool 2018-08-28 9:49:47 140102536005376 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Highest supported file format is Barracuda. 2018-08-28 9:49:47 140103925024640 [Note] InnoDB: Starting crash recovery from checkpoint LSN=232724331610 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Starting final batch to recover 308 pages from redo log. 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Last binlog file './master2-bin.000022', position 97193954 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: 128 out of 128 rollback segments are active. 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Creating shared tablespace for temporary tables 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: Waiting for purge to start 2018-08-28 9:49:48 140103925024640 [Note] InnoDB: 5.7.22 started; log sequence number 232725820508 2018-08-28 9:49:48 140101757691648 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2018-08-28 9:49:48 140103925024640 [Note] Plugin 'FEEDBACK' is disabled. 2018-08-28 9:49:48 140103925024640 [Note] Recovering after a crash using master2-bin 2018-08-28 9:49:48 140103925024640 [Note] Starting crash recovery... 2018-08-28 9:49:48 140103925024640 [Note] Crash recovery finished. 2018-08-28 9:49:48 140103925024640 [Note] Server socket created on IP: '::'. 2018-08-28 9:49:48 140103925024640 [Warning] 'proxies_priv' entry '@% root@mariadb' ignored in --skip-name-resolve mode. 2018-08-28 9:49:48 140103925024640 [Note] Reading of all Master_info entries succeded 2018-08-28 9:49:48 140103925024640 [Note] Added new Master_info '' to hash table 2018-08-28 9:49:48 140103925024640 [Note] Failed to execute mysql_file_stat on file './master2-relay-bin.002410' 2018-08-28 09:49:49 0x7f6c117fa700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.16/storage/innobase/btr/btr0cur.cc line 319 InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ InnoDB: about forcing recovery. 180828 9:49:49 [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.2.16-MariaDB-10.2.16+maria~jessie-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=102 thread_count=7 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759917 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f6bfc0009a8 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 = 0x7f6c117f9dc8 thread_stack 0x49000 mysqld(my_print_stacktrace+0x2e)[0x564eed883bae] mysqld(handle_fatal_signal+0x345)[0x564eed301795] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f6c7c6cd890] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f6c7aa57067] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f6c7aa58448] mysqld(+0x42330e)[0x564eed09b30e] mysqld(+0x9925b8)[0x564eed60a5b8] mysqld(+0x99da39)[0x564eed615a39] mysqld(+0x9a0e03)[0x564eed618e03] mysqld(+0x8f7915)[0x564eed56f915] mysqld(+0x8f8fe9)[0x564eed570fe9] mysqld(+0x8b6848)[0x564eed52e848] mysqld(+0x926ef6)[0x564eed59eef6] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f6c7c6c6064] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6c7ab0a62d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): Connection ID (thread ID): 2 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on 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. Fatal signal 11 while backtracing