mysql can't run, here is the log 2023-07-22 7:11:16 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2023-07-22 7:11:16 0 [Note] InnoDB: Uses event mutexes 2023-07-22 7:11:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2023-07-22 7:11:16 0 [Note] InnoDB: Number of pools: 1 2023-07-22 7:11:16 0 [Note] InnoDB: Using generic crc32 instructions 2023-07-22 7:11:16 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2023-07-22 7:11:16 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M 2023-07-22 7:11:16 0 [Note] InnoDB: Completed initialization of buffer pool 2023-07-22 7:11:16 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2023-07-22 7:11:16 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=43192320976 2023-07-22 7:11:17 0 [Note] InnoDB: Transaction 49826004 was in the XA prepared state. 2023-07-22 7:11:17 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo 2023-07-22 7:11:17 0 [Note] InnoDB: Trx id counter is 49826005 2023-07-22 7:11:17 0 [Note] InnoDB: Starting final batch to recover 22 pages from redo log. 2023-07-22 07:11:17 0x153a829f4700 InnoDB: Assertion failure in file /home/baota/deb/mariadb/mariadb104/bt-mariadb104-10.4.14/storage/innobase/log/log0recv.cc line 1519 InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table) 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/innodb-recovery-modes/ InnoDB: about forcing recovery. 230722 7:11: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.4.14-MariaDB-log key_buffer_size=1073741824 read_buffer_size=16777216 max_used_connections=0 max_threads=502 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17511500 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 /www/server/mysql/bin/mysqld(my_print_stacktrace+0x2d)[0x559c88f0e66d] /www/server/mysql/bin/mysqld(handle_fatal_signal+0x54d)[0x559c88a4982d] /lib/x86_64-linux-gnu/libpthread.so.0(+0x143c0)[0x153c6529f3c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x153c64a1d03b] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x153c649fc859] /www/server/mysql/bin/mysqld(+0x5a5f2f)[0x559c88746f2f] /www/server/mysql/bin/mysqld(+0x589845)[0x559c8872a845] /www/server/mysql/bin/mysqld(+0xab07af)[0x559c88c517af] /www/server/mysql/bin/mysqld(+0x589c38)[0x559c8872ac38] /www/server/mysql/bin/mysqld(+0x5ac87b)[0x559c8874d87b] /www/server/mysql/bin/mysqld(+0xbef7be)[0x559c88d907be] /www/server/mysql/bin/mysqld(+0xb349b8)[0x559c88cd59b8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x153c65293609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x153c64af9163] 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. Writing a core file... Working directory at /www/server/data Resource Limits: Fatal signal 11 while backtracing

Can't Start MySQL

chuenk

aaPanel_Kern

Hello, after taking a snapshot backup of the server, please refer to this tutorial to see if it can be resolved?
https://www.aapanel.com/forum/d/13216-mysqlmariadb-innodb-storage-engine-damage-solution

chuenk

Can't start

aaPanel_Kern

chuenk
Hello, after taking a snapshot backup of the server, please refer to this tutorial to see if it can be resolved?
https://www.aapanel.com/forum/d/13216-mysqlmariadb-innodb-storage-engine-damage-solution

chuenk

aaPanel_Kern not solved

chuenk

aaPanel_Kern
can't start in here

aaPanel_Kern

chuenk
I suggest you follow the tutorial first, can it be solved?

chuenk

aaPanel_Kern I have followed the tutorial but when the mysql start part failed

chuenk

aaPanel_Kern
during stage 4, starting mysql could not be done

chuenk

aaPanel_Kern thank you, mysql can be done by changing the innodb_force_recovery parameter

aaPanel_Kern

chuenk
It is recommended that you carefully review the tutorial once and then do related operations Here you can set 1-6
Or let a professional security company help you deal with

aaP_marufkhan0498

chuenk which parameter you used?

aaPanel_Kern

Ok, take care to back up your database daily. If there is a problem, please check the log of the relevant program as soon as possible

chuenk

aaPanel_Kern mysql error again, how do I uninstall mysql, it can't be uninstalled in the app store

aaPanel_Kern

chuenk
Use the ssh tool to execute the command and check the mysql error log:
cat /www/server/data/*.err|grep -i -C 10 error