2018-04-26 11:52:42 0 [Note] /usr/sbin/mysqld (mysqld 10.3.6-MariaDB) starting as process 22007 ...
2018-04-26 11:52:42 0 [Note] InnoDB: For Galera, using innodb_lock_schedule_algorithm=fcfs
2018-04-26 11:52:42 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-26 11:52:42 0 [Note] InnoDB: Uses event mutexes
2018-04-26 11:52:42 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-04-26 11:52:42 0 [Note] InnoDB: Using Linux native AIO
2018-04-26 11:52:42 0 [Note] InnoDB: Number of pools: 1
2018-04-26 11:52:42 0 [Note] InnoDB: Using generic crc32 instructions
2018-04-26 11:52:42 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-04-26 11:52:42 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-26 11:52:42 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-26 11:52:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=68953003113
2018-04-26 11:52:42 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2018-04-26 11:52:42 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2018-04-26 11:52:42 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2018-04-26 11:52:42 0 [ERROR] InnoDB: Cannot open datafile for read-only: './tpcc/STOCK.ibd' OS error: 71
2018-04-26 11:52:42 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2018-04-26 11:52:42 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2018-04-26 11:52:42 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2018-04-26 11:52:42 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``tpcc`.`STOCK``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2018-04-26 11:52:42 0 [Warning] InnoDB: Ignoring tablespace for `tpcc`.`STOCK` because it could not be opened.
2018-04-26 11:52:42 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2018-04-26 11:52:42 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2018-04-26 11:52:42 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2018-04-26 11:52:42 0 [ERROR] InnoDB: Cannot open datafile for read-only: './tpcc/WAREHOUSE.ibd' OS error: 71
2018-04-26 11:52:42 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2018-04-26 11:52:42 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2018-04-26 11:52:42 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2018-04-26 11:52:42 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``tpcc`.`WAREHOUSE``. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2018-04-26 11:52:42 0 [Warning] InnoDB: Ignoring tablespace for `tpcc`.`WAREHOUSE` because it could not be opened.
2018-04-26 11:52:42 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-04-26 11:52:42 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-04-26 11:52:42 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-04-26 11:52:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-04-26 11:52:42 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-04-26 11:52:42 0 [Note] InnoDB: Waiting for purge to start
2018-04-26 11:52:42 1 [ERROR] [FATAL] InnoDB: Trying to read page number 105795 in space 174, space name tpcc/ORDER_LINE, which is outside the tablespace bounds. Byte offset 0, len 16384
180426 11:52: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.3.6-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467387 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fbe140009a8
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 = 0x7fbe1effcc70 thread_stack 0x49000
2018-04-26 11:52:42 0 [Note] InnoDB: 5.7.21 started; log sequence number 68953003122; transaction id 822399
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x561939cf3f1e]
/usr/sbin/mysqld(handle_fatal_signal+0x357)[0x561939796807]
sigaction.c:0(__restore_rt)[0x7fbe5acc35e0]
:0(__GI_raise)[0x7fbe591d01f7]
:0(__GI_abort)[0x7fbe591d18e8]
/usr/sbin/mysqld(+0xa9b463)[0x561939abd463]
/usr/sbin/mysqld(+0x4cb163)[0x5619394ed163]
ut/ut0ut.cc:793(ib::fatal::~fatal())[0x561939b6b121]
fil/fil0fil.cc:4357(fil_report_invalid_page_access(unsigned long, unsigned long, char const*, unsigned long, unsigned long, bool))[0x561939b1fe85]
fil/fil0fil.cc:4598(fil_io(IORequest const&, bool, page_id_t const&, page_size_t const&, unsigned long, unsigned long, void*, void*, bool))[0x561939afd9e6]
buf/buf0rea.cc:197(buf_read_page(page_id_t const&, page_size_t const&))[0x561939adc99e]
buf/buf0buf.cc:4385(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t*, unsigned long, char const*, unsigned int, mtr_t*, dberr_t*))[0x561939a4249c]
btr/btr0cur.cc:1309(btr_cur_search_to_nth_level_func(dict_index_t*, unsigned long, dtuple_t const*, page_cur_mode_t, unsigned long, btr_cur_t*, rw_lock_t*, char const*, unsigned int, mtr_t*, unsigned long))[0x561939a43a87]
include/btr0pcur.ic:456(btr_pcur_open_low(dict_index_t*, unsigned long, dtuple_t const*, page_cur_mode_t, unsigned long, btr_pcur_t*, char const*, unsigned int, unsigned long, mtr_t*) [clone .constprop.38])[0x561939a3e51f]
include/page0page.h:224(row_search_on_row_ref(btr_pcur_t*, unsigned long, dict_table_t const*, dtuple_t const*, mtr_t*))[0x561939a40a3b]
row/row0purge.cc:106(row_purge_reset_trx_id(purge_node_t*, mtr_t*))[0x561939a41563]
include/dyn0buf.h:198(dyn_buf_t<512ul>::erase())[0x5619399fef43]
row/row0purge.cc:1111(row_purge_step(que_thr_t*))[0x561939a70c7d]
pthread_create.c:0(start_thread)[0x7fbe5acbbe25]
/lib64/libc.so.6(clone+0x6d)[0x7fbe5929334d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): is an invalid pointer
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,split_materialized=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.

We think the query pointer is invalid, but we will try to print it anyway.
Query: