Table *** Is Marked As Crashed And Should Be Repaired

Home » CentOS » Table *** Is Marked As Crashed And Should Be Repaired
CentOS 1 Comment

Hi,

I’ve started migrating my sites to mariadb which is supposed to be a drop-in replacement of mysql. Both run on the same C6 box. DB folders were moved to a new location after both DB servers were stopped and properly upgraded. There were no reboots or power failures. Nevertheless I see these error messages in the logs:

# cat /var/opt/rh/rh-mariadb102/log/mariadb/mariadb.log
…
2020-11-29 16:38:23 139882501732320 [Note]
/opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: ‘10.2.22-MariaDB’ socket:
‘/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock’ port: 3307 MariaDB Server
2020-11-29 16:38:23 139882394105600 [Warning] Access denied for user
‘UNKNOWN_MYSQL_USER’@’localhost’ (using password: NO)
2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_wc_customer_lookup’ is marked as crashed and should be repaired
2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table
‘wp_wc_customer_lookup’ is marked as crashed and should be repaired
2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_wc_customer_lookup’ is marked as crashed and should be repaired
2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table
‘wp_wc_customer_lookup’ is marked as crashed and should be repaired
2020-11-29 16:39:37 139882394105600 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_wc_customer_lookup’
…
2020-11-29 17:16:17 140059421116384 [Note]
/opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: ‘10.2.22-MariaDB’ socket:
‘/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock’ port: 3307 MariaDB Server
2020-11-29 17:16:18 140059356550912 [Warning] Access denied for user
‘UNKNOWN_MYSQL_USER’@’localhost’ (using password: NO)
2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_options’ is marked as crashed and should be repaired
2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table ‘wp_options’ is marked as crashed and should be repaired
2020-11-29 17:20:01 140059356550912 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_options’
2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_posts’ is marked as crashed and should be repaired
2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table ‘wp_posts’ is marked as crashed and should be repaired
2020-11-29 17:20:02 140059356550912 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_posts’
2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_actionscheduler_claims’ is marked as crashed and should be repaired
2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table
‘wp_actionscheduler_claims’ is marked as crashed and should be repaired
2020-11-29 17:20:02 140059356550912 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_actionscheduler_claims’
2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_usermeta’ is marked as crashed and should be repaired
2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table ‘wp_usermeta’ is marked as crashed and should be repaired
2020-11-29 17:22:28 140059356550912 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_usermeta’
2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_woocommerce_sessions’ is marked as crashed and should be repaired
2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table
‘wp_woocommerce_sessions’ is marked as crashed and should be repaired
2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table
‘./wordpress@002dstorefront/wp_woocommerce_sessions’ is marked as crashed and should be repaired
2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table
‘wp_woocommerce_sessions’ is marked as crashed and should be repaired
2020-11-29 17:22:31 140059356550912 [Warning] Checking table:
‘./wordpress@002dstorefront/wp_woocommerce_sessions’
…

Note that after the crashed table was repaired mariadb reported multiple crashed tables in the same DB after restart. Any pointers? Never had such problems with mysqld. Is mariadb reliable and stable at all?

# cat /etc/CentOS-release CentOS release 6.10 (Final)

# rpm -qa ‘*maria*’
rh-mariadb102-mariadb-server-utils-10.2.22-1.el6.x86_64
rh-mariadb102-mariadb-common-10.2.22-1.el6.x86_64
rh-mariadb102-mariadb-10.2.22-1.el6.x86_64
rh-mariadb102-mariadb-server-10.2.22-1.el6.x86_64
rh-mariadb102-mariadb-config-10.2.22-1.el6.x86_64
rh-mariadb102-mariadb-errmsg-10.2.22-1.el6.x86_64
rh-mariadb102-runtime-3.0-5.el6.x86_64

TIA, AK

One thought on - Table *** Is Marked As Crashed And Should Be Repaired

  • OK. It turns out to be not such a big deal. The MyISAM table is declared crashed if the number of open file handles doesn’t match the counter in the header. MySQL 5.1 doesn’t care and doesn’t write these warnings to the logs but it still can be detected and fixed with mysqlcheck:

    # mysqlcheck –all-databases
    … wordpress-test.wp_actionscheduler_claims warning : 3 clients are using or haven’t closed the table properly status : OK
    … wordpress-test.wp_options warning : 3 clients are using or haven’t closed the table properly status : OK

    So run mysqlcheck –databases … before moving the DBs to a new location or import the data from a mysql dump.

    пн, 30 нояб. 2020 г. в 15:28, Александр Кириллов :

    CentOS mailing list CentOS@CentOS.org https://lists.CentOS.org/mailman/listinfo/CentOS