Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: Error: trying to load index PRIMARY for table nextcloud/oc_accounts                                            [490/1882]
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: but the index tree has been freed!
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: Index is corrupt but forcing load into data dictionary
Apr 24 15:41:40 kvmserver kernel: [161788.680433] blk_update_request: I/O error, dev vda, sector 1011296
Apr 24 15:41:40 kvmserver mysqld[3525]: 2019-04-24 15:41:40 140712052283136 [ERROR] InnoDB: Tried to read 16384 bytes at offset 5029888. Was only able to read 0.
Apr 24 15:41:40 kvmserver mysqld[3525]: FAIL2019-04-24 15:41:40 7ffa13e45700  InnoDB: Assertion failure in thread 140712052283136 in file buf0rea.cc line 273
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: We intentionally generate a memory trap.
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: If you get repeated assertion failures or crashes, even
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: immediately after the mysqld startup, there may be
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Apr 24 15:41:40 kvmserver mysqld[3525]: InnoDB: about forcing recovery.
Apr 24 15:41:40 kvmserver mysqld[3525]: 190424 15:41:40 [ERROR] mysqld got signal 6 ;
Apr 24 15:41:40 kvmserver mysqld[3525]: This could be because you hit a bug. It is also possible that this binary
Apr 24 15:41:40 kvmserver mysqld[3525]: or one of the libraries it was linked against is corrupt, improperly built,
Apr 24 15:41:40 kvmserver mysqld[3525]: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 24 15:41:40 kvmserver mysqld[3525]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 24 15:41:40 kvmserver mysqld[3525]: We will try our best to scrape up some info that will hopefully help
Apr 24 15:41:40 kvmserver mysqld[3525]: diagnose the problem, but since we have already crashed,
Apr 24 15:41:40 kvmserver mysqld[3525]: something is definitely wrong and this may fail.
Apr 24 15:41:40 kvmserver mysqld[3525]: Server version: 10.1.37-MariaDB-0+deb9u1
Apr 24 15:41:40 kvmserver mysqld[3525]: key_buffer_size=16384
Apr 24 15:41:40 kvmserver mysqld[3525]: read_buffer_size=262144
Apr 24 15:41:40 kvmserver mysqld[3525]: max_used_connections=1
Apr 24 15:41:40 kvmserver mysqld[3525]: max_threads=153
Apr 24 15:41:40 kvmserver mysqld[3525]: thread_count=1
Apr 24 15:41:40 kvmserver mysqld[3525]: It is possible that mysqld could use up to
Apr 24 15:41:40 kvmserver mysqld[3525]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 52131 K  bytes of memory
Apr 24 15:41:40 kvmserver mysqld[3525]: Hope that's ok; if not, decrease some variables in the equation.
Apr 24 15:41:40 kvmserver mysqld[3525]: Thread pointer: 0x7ffa10fc9008
Apr 24 15:41:40 kvmserver mysqld[3525]: Attempting backtrace. You can use the following information to find out
Apr 24 15:41:40 kvmserver mysqld[3525]: where mysqld died. If you see no messages after this, something went
Apr 24 15:41:40 kvmserver mysqld[3525]: terribly wrong...
Apr 24 15:41:40 kvmserver mysqld[3525]: stack_bottom = 0x7ffa13e44cb8 thread_stack 0x20000
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c012d5239e]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55c01289397d]
Apr 24 15:41:40 kvmserver mysqld[3525]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7ffa13b2e0e0]
Apr 24 15:41:40 kvmserver mysqld[3525]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7ffa1269bfff]
Apr 24 15:41:40 kvmserver mysqld[3525]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7ffa1269d42a]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x99908f)[0x55c012c8808f]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x9998d9)[0x55c012c888d9]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x979534)[0x55c012c68534]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x95809c)[0x55c012c4709c]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8f2c91)[0x55c012be1c91]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8f3987)[0x55c012be2987]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8f5dbb)[0x55c012be4dbb]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8b666c)[0x55c012ba566c]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8b6f52)[0x55c012ba5f52]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8e2226)[0x55c012bd1226]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x8226b7)[0x55c012b116b7]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z15ha_delete_tableP3THDP10handlertonPKcS4_S4_b+0x15b)[0x55c01289b90b]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z23mysql_rm_table_no_locksP3THDP10TABLE_LISTbbbbb+0x78f)[0x55c012784f6f]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(+0x3e6284)[0x55c0126d5284]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6322)[0x55c012700872]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x311)[0x55c012703801]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2615)[0x55c012707165]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z10do_commandP3THD+0x179)[0x55c0127079a9]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1d2)[0x55c0127d6842]
Apr 24 15:41:40 kvmserver mysqld[3525]: /usr/sbin/mysqld(handle_one_connection+0x40)[0x55c0127d69a0]
Apr 24 15:41:40 kvmserver mysqld[3525]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7ffa13b244a4]
Apr 24 15:41:40 kvmserver mysqld[3525]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7ffa12751d0f]
Apr 24 15:41:40 kvmserver mysqld[3525]: Trying to get some variables.
Apr 24 15:41:40 kvmserver mysqld[3525]: Some pointers may be invalid and cause the dump to abort.
Apr 24 15:41:40 kvmserver mysqld[3525]: Query (0x7ff9ecc3b020): DROP DATABASE nextcloud
Apr 24 15:41:40 kvmserver mysqld[3525]: Connection ID (thread ID): 2
Apr 24 15:41:40 kvmserver mysqld[3525]: Status: NOT_KILLED
Apr 24 15:41:40 kvmserver mysqld[3525]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersec
tion=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,semijo
in=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
=off
Apr 24 15:41:40 kvmserver mysqld[3525]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 24 15:41:40 kvmserver mysqld[3525]: information that should help you find out what is causing the crash.
Apr 24 15:41:40 kvmserver systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
Apr 24 15:41:40 kvmserver systemd[1]: mariadb.service: Unit entered failed state.
Apr 24 15:41:40 kvmserver systemd[1]: mariadb.service: Failed with result 'signal'.
Apr 24 15:41:45 kvmserver systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
Apr 24 15:41:45 kvmserver systemd[1]: Stopped MariaDB 10.1.37 database server.
Apr 24 15:41:45 kvmserver systemd[1]: Starting MariaDB 10.1.37 database server...