2018-07-03  7:57:50 139970909173632 [Note] mysqld (mysqld 10.2.15-MariaDB-10.2.15+maria~jessie-log) starting as process 1 ...


2018-07-03  7:57:50 139970909173632 [Note] Failed to execute mysql_file_stat on file './master2-bin.000070'


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Uses event mutexes


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Compressed tables use zlib 1.2.8


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Using Linux native AIO


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Number of pools: 1


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Using SSE2 crc32 instructions


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Completed initialization of buffer pool


2018-07-03  7:57:50 139969512273664 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Highest supported file format is Barracuda.


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Starting crash recovery from checkpoint LSN=100659872460


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 113 row operations to undo


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Trx id counter is 24920320


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Starting final batch to recover 27 pages from redo log.


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Last binlog file './master2-bin.000031', position 55381727


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: 128 out of 128 rollback segments are active.


2018-07-03  7:57:50 139969503880960 [Note] InnoDB: Starting in background the rollback of recovered transactions


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Creating shared tablespace for temporary tables


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: File './ibtmp1' size is now 12 MB.


2018-07-03  7:57:50 139970909173632 [Note] InnoDB: 5.7.22 started; log sequence number 100659970540


2018-07-03  7:57:50 139968865355520 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool


InnoDB: Next record offset is nonsensical 20525 in record at offset 0


InnoDB: rec address 0x7f4d6635c000, space id 0, page 23525


2018-07-03 07:57:50 0x7f4d308ee700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.15/storage/innobase/include/page0page.ic line 678


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.


180703  7:57:50 [ERROR] mysqld got signal 6 ;


This could be because you hit a bug. It is also possible that this binary


or one of the libraries it was linked against is corrupt, improperly built,


or misconfigured. This error can also be caused by malfunctioning hardware.




To report this bug, see https://mariadb.com/kb/en/reporting-bugs




We will try our best to scrape up some info that will hopefully help


diagnose the problem, but since we have already crashed, 


something is definitely wrong and this may fail.




Server version: 10.2.15-MariaDB-10.2.15+maria~jessie-log


key_buffer_size=134217728


read_buffer_size=2097152


max_used_connections=0


max_threads=102


thread_count=5


It is possible that mysqld could use up to 


key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759911 K  bytes of memory


Hope that's ok; if not, decrease some variables in the equation.




Thread pointer: 0x0


Attempting backtrace. You can use the following information to find out


where mysqld died. If you see no messages after this, something went


terribly wrong...


stack_bottom = 0x0 thread_stack 0x49000


mysqld(my_print_stacktrace+0x2e)[0x5561673bbb6e]


mysqld(handle_fatal_signal+0x345)[0x556166e3a185]


2018-07-03  7:57:50 139970909173632 [Note] Plugin 'FEEDBACK' is disabled.


2018-07-03  7:57:50 139970909173632 [Note] Recovering after a crash using master2-bin


2018-07-03  7:57:50 139970909173632 [Note] Starting crash recovery...


2018-07-03  7:57:50 139970909173632 [Note] Crash recovery finished.


/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f4d84100890]


/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4d8248a067]


/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4d8248b448]


mysqld(+0x42229c)[0x556166bd229c]


mysqld(+0x89773d)[0x55616704773d]


mysqld(+0x99bf22)[0x55616714bf22]


mysqld(+0x8f8f25)[0x5561670a8f25]


mysqld(+0x8fa776)[0x5561670aa776]


mysqld(+0xa9ae5f)[0x55616724ae5f]


mysqld(+0xa9cbd0)[0x55616724cbd0]


mysqld(+0x91085e)[0x5561670c085e]


mysqld(+0x8b5893)[0x556167065893]


mysqld(+0x9577b7)[0x5561671077b7]


mysqld(+0x9586b1)[0x5561671086b1]


/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f4d840f9064]


/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4d8253d62d]


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-07-03  7:58:52 139934388946816 [Note] mysqld (mysqld 10.2.15-MariaDB-10.2.15+maria~jessie-log) starting as process 1 ...


2018-07-03  7:58:52 139934388946816 [Note] Failed to execute mysql_file_stat on file './master2-bin.000070'


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Uses event mutexes


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Compressed tables use zlib 1.2.8


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Using Linux native AIO


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Number of pools: 1


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Using SSE2 crc32 instructions


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Completed initialization of buffer pool


2018-07-03  7:58:52 139932996658944 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Highest supported file format is Barracuda.


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Starting crash recovery from checkpoint LSN=100659872460


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 113 row operations to undo


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Trx id counter is 24920320


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Starting final batch to recover 27 pages from redo log.


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Last binlog file './master2-bin.000031', position 55381727


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: 128 out of 128 rollback segments are active.


2018-07-03  7:58:52 139932920182528 [Note] InnoDB: Starting in background the rollback of recovered transactions


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Creating shared tablespace for temporary tables


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: File './ibtmp1' size is now 12 MB.


2018-07-03  7:58:52 139934388946816 [Note] InnoDB: 5.7.22 started; log sequence number 100659970540


2018-07-03  7:58:52 139932492351232 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool


InnoDB: Next record offset is nonsensical 20525 in record at offset 0


InnoDB: rec address 0x7f44e635c000, space id 0, page 23525


2018-07-03 07:58:52 0x7f44abfff700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.15/storage/innobase/include/page0page.ic line 678


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.


180703  7:58:52 [ERROR] mysqld got signal 6 ;


This could be because you hit a bug. It is also possible that this binary


or one of the libraries it was linked against is corrupt, improperly built,


or misconfigured. This error can also be caused by malfunctioning hardware.




To report this bug, see https://mariadb.com/kb/en/reporting-bugs




We will try our best to scrape up some info that will hopefully help


diagnose the problem, but since we have already crashed, 


something is definitely wrong and this may fail.




Server version: 10.2.15-MariaDB-10.2.15+maria~jessie-log


key_buffer_size=134217728


read_buffer_size=2097152


max_used_connections=0


max_threads=102


thread_count=5


It is possible that mysqld could use up to 


key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759911 K  bytes of memory


Hope that's ok; if not, decrease some variables in the equation.




Thread pointer: 0x0


Attempting backtrace. You can use the following information to find out


where mysqld died. If you see no messages after this, something went


terribly wrong...


stack_bottom = 0x0 thread_stack 0x49000


mysqld(my_print_stacktrace+0x2e)[0x55e5739d5b6e]


mysqld(handle_fatal_signal+0x345)[0x55e573454185]


2018-07-03  7:58:52 139934388946816 [Note] Plugin 'FEEDBACK' is disabled.


2018-07-03  7:58:52 139934388946816 [Note] Recovering after a crash using master2-bin


2018-07-03  7:58:52 139934388946816 [Note] Starting crash recovery...


2018-07-03  7:58:52 139934388946816 [Note] Crash recovery finished.


/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f4503499890]


/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4501823067]


/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4501824448]


mysqld(+0x42229c)[0x55e5731ec29c]


mysqld(+0x89773d)[0x55e57366173d]


mysqld(+0x99bf22)[0x55e573765f22]


mysqld(+0x8f8f25)[0x55e5736c2f25]


mysqld(+0x8fa776)[0x55e5736c4776]


mysqld(+0xa9ae5f)[0x55e573864e5f]


mysqld(+0xa9cbd0)[0x55e573866bd0]


mysqld(+0x91085e)[0x55e5736da85e]


mysqld(+0x8b5893)[0x55e57367f893]


mysqld(+0x9577b7)[0x55e5737217b7]


mysqld(+0x9586b1)[0x55e5737226b1]


/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f4503492064]


/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f45018d662d]


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-07-03  7:59:54 139899159861120 [Note] mysqld (mysqld 10.2.15-MariaDB-10.2.15+maria~jessie-log) starting as process 1 ...


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Uses event mutexes


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Compressed tables use zlib 1.2.8


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Using Linux native AIO


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Number of pools: 1


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Using SSE2 crc32 instructions


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Completed initialization of buffer pool


2018-07-03  7:59:54 139897764505344 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Highest supported file format is Barracuda.


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Starting crash recovery from checkpoint LSN=100659872460


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 113 row operations to undo


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Trx id counter is 24920320


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Starting final batch to recover 27 pages from redo log.


2018-07-03  7:59:54 139899159861120 [Note] InnoDB: Last binlog file './master2-bin.000031', position 55381727


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: 128 out of 128 rollback segments are active.


2018-07-03  7:59:55 139897688028928 [Note] InnoDB: Starting in background the rollback of recovered transactions


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: Creating shared tablespace for temporary tables


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: File './ibtmp1' size is now 12 MB.


2018-07-03  7:59:55 139899159861120 [Note] InnoDB: Waiting for purge to start


InnoDB: Next record offset is nonsensical 20525 in record at offset 0


InnoDB: rec address 0x7f3cb235c000, space id 0, page 23525


2018-07-03 07:59:55 0x7f3c77fff700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.15/storage/innobase/include/page0page.ic line 678


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.


180703  7:59:55 [ERROR] mysqld got signal 6 ;


This could be because you hit a bug. It is also possible that this binary


or one of the libraries it was linked against is corrupt, improperly built,


or misconfigured. This error can also be caused by malfunctioning hardware.




To report this bug, see https://mariadb.com/kb/en/reporting-bugs




We will try our best to scrape up some info that will hopefully help


diagnose the problem, but since we have already crashed, 


something is definitely wrong and this may fail.




Server version: 10.2.15-MariaDB-10.2.15+maria~jessie-log


key_buffer_size=134217728


read_buffer_size=2097152


max_used_connections=0


max_threads=102


thread_count=4


It is possible that mysqld could use up to 


key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759911 K  bytes of memory


Hope that's ok; if not, decrease some variables in the equation.




Thread pointer: 0x0


Attempting backtrace. You can use the following information to find out


where mysqld died. If you see no messages after this, something went


terribly wrong...


stack_bottom = 0x0 thread_stack 0x49000


mysqld(my_print_stacktrace+0x2e)[0x55742475cb6e]


mysqld(handle_fatal_signal+0x345)[0x5574241db185]


/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f3ccf786890]


/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f3ccdb10067]


/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f3ccdb11448]


mysqld(+0x42229c)[0x557423f7329c]


mysqld(+0x89773d)[0x5574243e873d]


mysqld(+0x99bf22)[0x5574244ecf22]


mysqld(+0x8f8f25)[0x557424449f25]


mysqld(+0x8fa776)[0x55742444b776]


mysqld(+0xa9ae5f)[0x5574245ebe5f]


mysqld(+0xa9cbd0)[0x5574245edbd0]


mysqld(+0x91085e)[0x55742446185e]


mysqld(+0x8b5893)[0x557424406893]


mysqld(+0x9577b7)[0x5574244a87b7]


mysqld(+0x9586b1)[0x5574244a96b1]


/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f3ccf77f064]


/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3ccdbc362d]


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