Issue Innodb Corruption

[deantenea]

Server operating system version

Debian 9.13

Plesk version and microupdate number

18.0.43

Hello guys,
I'm having an issue with a Plesk server.
MySQL seems to be corrupted and won't restart, I cannot access the Plesk CP.

Any help is very appreciated.


Here is what i tried (but didn't work):

[mysqld]
innodb_force_recovery = 1
(tried from 1 to 6)
innodb_buffer_poool_chunk_size=13421778
(in /etc/mysql/mariadb.cnf )


Here are the errors in mysql logs:

2022-06-03 09:43:08 7f5fd6ad6d80 InnoDB: Assertion failure in thread 140049600310656 in file log0log.cc line 3787
InnoDB: Failing assertion: lsn == log_sys->lsn
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to System Dashboard - Jira
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: MySQL :: MySQL 5.6 Reference Manual :: 14.21.2 Forcing InnoDB Recovery
InnoDB: about forcing recovery.
220603 9:43:08 [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 MariaDB Community Bug Reporting

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)[0x56275244bc7e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x562751f99bdd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f5fd67440e0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f5fd52b1fff]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5fd52b342a]
/usr/sbin/mysqld(+0x883e35)[0x56275225ee35]
/usr/sbin/mysqld(+0x920c39)[0x5627522fbc39]
/usr/sbin/mysqld(+0x82b2f7)[0x5627522062f7]
/usr/sbin/mysqld(_Z22ha_finalize_handlertonP13st_plugin_int+0x34)[0x562751f9bc94]
/usr/sbin/mysqld(+0x434270)[0x562751e0f270]
/usr/sbin/mysqld(+0x4389ae)[0x562751e139ae]
/usr/sbin/mysqld(_Z15plugin_shutdownv+0x3d5)[0x562751e14a35]
/usr/sbin/mysqld(+0x381ac1)[0x562751d5cac1]
/usr/sbin/mysqld(unireg_abort+0x326)[0x562751d5fa76]
/usr/sbin/mysqld(+0x386dc9)[0x562751d61dc9]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4fb)[0x562751d6608b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f5fd529f2e1]
/usr/sbin/mysqld(_start+0x2a)[0x562751d5a06a]
The manual page at How to Produce a Full Stack Trace for mysqld contains
information that should help you find out what is causing the crash.

 

[Azurel]

You have already tried this?

https://support.plesk.com/hc/en-us/articles/213939865-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Linux-

 

[deantenea]

You have already tried this?

https://support.plesk.com/hc/en-us/articles/213939865-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Linux-

Yes, I tried up to point 5.


When I try to make a dump as per point 6:
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -Ns -uadmin psa -Ne"show databases" | grep -v information_schema | grep -v performance_schema > /root/db_list.txt

I got this error:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

 

[IgorG]

I got this error:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

Your MySQL server was not started in step 5. It is stopped, so step 6 cannot be performed. You need to figure out why the MySQL server did not start in step 5. If you're having trouble doing this, I suggest that you contact Plesk tech support for help.

 

[reirod]

Hello, I have some similar issue " Hbl77KP_wfls_role_counts The storage engine for the table doesn't support check " all the solutions I read is to ALTER to MyISAM but seems to be high risk operation... Some other easy way to solve it?

 

[reirod]

Hello, I have some similar issue " Hbl77KP_wfls_role_counts The storage engine for the table doesn't support check " all the solutions I read is to ALTER to MyISAM but seems to be high risk operation... Some other easy way to solve it?

Hello again, finally I tried the ALTER in one dump and solved.