• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Question SQL Server

UHolthausen

Regular Pleskian
Hello

Yesterday Plesk was very slow in building pages and I found this in Myysql log:
2020-03-01 7:41:45 139776344763776 [ERROR] mysqld: Table './mysql/user' is marked as crashed and should be repaired
2020-03-01 7:41:45 139776344763776 [Warning] Checking table: './mysql/user'
2020-03-01 7:41:45 139776344763776 [ERROR] mysql.user: 1 client is using or hasn't closed the table properly
2020-03-01 7:41:46 139776344763776 [ERROR] mysqld: Table './mysql/db' is marked as crashed and should be repaired
First I checked the system by diagnosis&repair, everything ok (green)
To be on the safe side also by Ppmyadmin then the affected database checked.
No errors were displayed, also per cli everything ok.
Nevertheless I stopped the SQL Server and restarted it. Result: still long loading times.
The loading time was long the whole day. In the evening the same error message appeared in the mysql log.
I let it go for now, this morning everything was ok again.
What could be the reason? The server was online for 21 days.
System:
Operating system: Debian 9.12
Plesk: 17.8.11 incl. last update
mysql Ver 15.1 Distrib 10.1.44-MariaDB
 
Try to repair this table at least with something like

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -Ne 'REPAIR TABLE example_db.corrupted_table'

I hope it will help.
 
Back
Top