MySQLd service failed to start (after restarting server)

• . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 4 ^ mysql-bin.013645 _ @ _ @ jPs r P[ - s;
  InnoDB: End of page dump
  2024-12-27T10:09:56.929068Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 1578372452, calculated checksums for field1: crc32 2395217053/2308769659, innodb 3166210881, none 3735928559, stored checksum in field2 427868128, calculated checksums for field2: crc32 2395217053/2308769659, innodb 1668512616, none 3735928559, page LSN 14 3559769244, low 4 bytes of LSN at page end 3559753075, page number (if stored to page already) 5, space id (if created with >= MySQL-4.1.1 and stored already) 0
  InnoDB: Page may be a transaction system page
  2024-12-27T10:09:56.929074Z 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
  2024-12-27T10:09:56.929076Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or, there was a failure in tagging the tablespace as corrupt.
  2024-12-27 17:09:56 0x148441035740 InnoDB: Assertion failure in thread 22558258976576 in file ut0ut.cc line 921
  InnoDB: We intentionally generate a memory trap.
  InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
  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.7/en/forcing-innodb-recovery.html
  InnoDB: about forcing recovery.
  10:09:56 UTC - 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.
  Attempting to collect some information that could help diagnose the problem.
  As this is a crash and something is definitely wrong, the information
  collection process might fail.

key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=500
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2185771 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 = 0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x40)[0x558642728e30]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x4f9)[0x558641f53a49]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x14844158e420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x14844107d00b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x14844105c859]
/www/server/mysql/bin/mysqld(+0x6516ae)[0x558641f176ae]
/www/server/mysql/bin/mysqld(+0x651983)[0x558641f17983]
/www/server/mysql/bin/mysqld(Z20buf_page_io_completeP10buf_page_tb+0x2d0)[0x558642952b80]
/www/server/mysql/bin/mysqld(+0x10b6b24)[0x55864297cb24]
/www/server/mysql/bin/mysqld(Z13buf_read_pageRK9page_id_tRK11page_size_t+0x4a)[0x55864297d28a]
/www/server/mysql/bin/mysqld(Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4c6)[0x558642950b06]
/www/server/mysql/bin/mysqld(Z31trx_rseg_get_n_undo_tablespacesPm+0x140)[0x5586428ed5e0]
/www/server/mysql/bin/mysqld(+0xff1a4d)[0x5586428b7a4d]
/www/server/mysql/bin/mysqld(Z34innobase_start_or_create_for_mysqlv+0x2c67)[0x5586428bb1e7]
/www/server/mysql/bin/mysqld(+0xeb2e4d)[0x558642778e4d]
/www/server/mysql/bin/mysqld(Z24ha_initialize_handlertonP13st_plugin_int+0x59)[0x558641fa4409]
/www/server/mysql/bin/mysqld(+0xc3b1c5)[0x5586425011c5]
/www/server/mysql/bin/mysqld(Z40plugin_register_builtin_and_init_core_sePiPPc+0x1f4)[0x558642503644]
/www/server/mysql/bin/mysqld(Z11mysqld_mainiPPc+0xbae)[0x558641f4f36e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x14844105e083]
/www/server/mysql/bin/mysqld(_start+0x2e)[0x558641f4422e]
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.

aaPanel_Kern Thanks, now solve, btw i need remove this syntax innodb_force_recovery = 1 from configuration ?

Hello, after backing up the database, delete this configuration.

aaP_teguhnds

Hello, please check if you have the latest error log?
cat /www/server/data/*.err|grep -i -C 10 error

aaP_rumireminder

@aaPanel_Kern Even i cant take my backup how i fix it its urgent

Hello, you need to know what the problem is before you can solve it. What operations have you done?
Is there an error message?

aaP_rumireminder

aaPanel_Kern yess

https://file.io/D0sYKILvfVUW
latest error log

@aaPanel_Kern

Help me

can't start mysql server!

As I understand that if MySQLd service isn’t starting after a server restart, it could be due to database corruption.

I would suggest you to follow below steps:

1. Check error logs using:
   sudo cat /var/log/mysql/error.log

This will show what’s causing the issue.

2. Force InnoDB recovery (if tables are corrupted):

Force InnoDB recovery (if tables are corrupted):

• Add innodb_force_recovery = 1 in my.cnf under [mysqld]

• Restart MySQL: sudo systemctl restart mysql

• You can explore tools like Stellar Repair for MySQL if corruption is severe.

Check permissions & disk space:
sudo chown -R mysql:mysql /var/lib/mysql
df -h # Check disk space

And yes if the issue persists then restoring from a backup might be the best option also. Try and see!