0

I have a problem that mysql doesn't start anymore although nothing has been changed. The following error message appears when starting mysql.

This is the Error-log:

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.1.48-MariaDB-0+deb9u2
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352468 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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b3e361ac7e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55b3e3168bdd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f93ad2880e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f93abdf5fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f93abdf742a]
/usr/sbin/mysqld(+0x83e2db)[0x55b3e33e82db]
/usr/sbin/mysqld(+0x9e58c3)[0x55b3e358f8c3]
/usr/sbin/mysqld(+0x9a578c)[0x55b3e354f78c]
/usr/sbin/mysqld(+0x9a698b)[0x55b3e355098b]
/usr/sbin/mysqld(+0x9863db)[0x55b3e35303db]
/usr/sbin/mysqld(+0x94408a)[0x55b3e34ee08a]
/usr/sbin/mysqld(+0x936fd4)[0x55b3e34e0fd4]
/usr/sbin/mysqld(+0x937b55)[0x55b3e34e1b55]
/usr/sbin/mysqld(+0x938d7e)[0x55b3e34e2d7e]
/usr/sbin/mysqld(+0x9204ec)[0x55b3e34ca4ec]
/usr/sbin/mysqld(+0x834f41)[0x55b3e33def41]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x55b3e316adc2]
/usr/sbin/mysqld(+0x43bba5)[0x55b3e2fe5ba5]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7da)[0x55b3e2fe720a]
/usr/sbin/mysqld(+0x386733)[0x55b3e2f30733]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4fb)[0x55b3e2f3508b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f93abde32e1]
/usr/sbin/mysqld(_start+0x2a)[0x55b3e2f2906a]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: The InnoDB memory heap is disabled
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Using Linux native AIO
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Using SSE crc32 instructions
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Completed initialization of buffer pool
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Highest supported file format is Barracuda.
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Starting crash recovery from checkpoint LSN=4255497475575
2022-07-27 15:52:27 140672099548544 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2 log sequence number 4255498538021
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 4 log sequence number 4255498554636
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 5 log sequence number 4255498490648
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 6 log sequence number 4255498591148
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 1476 log sequence number 4255498468584
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 7602 log sequence number 4255498591148
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 45 log sequence number 4255498557219
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 510 log sequence number 4255498557219
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 46 log sequence number 4255498591380
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 1500 log sequence number 4255498540444
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 9288 log sequence number 4255498591380
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 47 log sequence number 4255498450668
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 9337 log sequence number 4255498450668
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 5650 log sequence number 4255498488034
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 48 log sequence number 4255498591595
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 7576 log sequence number 4255498591595
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 1775 log sequence number 4255498519575
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 49 log sequence number 4255498508439
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 7560 log sequence number 4255498508439
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 50 log sequence number 4255498592245
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2132 log sequence number 4255498557336
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 405 log sequence number 4255498540898
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 51 log sequence number 4255498594986
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2112 log sequence number 4255498594986
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 52 log sequence number 4255498591822
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2135 log sequence number 4255498508694
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 53 log sequence number 4255498586100
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2152 log sequence number 4255498586100
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 5686 log sequence number 4255498469739
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 54 log sequence number 4255498508933
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 7564 log sequence number 4255498508933
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 55 log sequence number 4255498592476
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 499 log sequence number 4255498592476
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 56 log sequence number 4255498509011
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 7579 log sequence number 4255498509011
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 5674 log sequence number 4255498541812
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 57 log sequence number 4255498592691
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 9284 log sequence number 4255498592691
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 58 log sequence number 4255498586233
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2138 log sequence number 4255498586233
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 59 log sequence number 4255498593110
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 438 log sequence number 4255498568089
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 60 log sequence number 4255498586272
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 7ff0c685fd80 InnoDB: Error: page 2149 log sequence number 4255498586272
InnoDB: is in the future! Current system log sequence number 4255498448416.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2022-07-27 15:52:27 140672099548544 [ERROR] InnoDB: Trying to access page number 326346753 in space 0 space name ./ibdata1, which is outside the tablespace bounds. Byte offset 0, len 16384 i/o type 10.Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
2022-07-27 15:52:27 7ff0c685fd80  InnoDB: Assertion failure in thread 140672099548544 in file ha_innodb.cc line 21944
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
220727 15:52:27 [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.

Can maybe anyone heelp me.

it is important to keep the data

Kind regards christoph

1
  • 1
    Your database appears to be corrupted. Restore it from the backup, which you undoubtedly have, since, as you say, "it is important to keep the data".
    – mustaccio
    Jul 27 at 22:14

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.