Support

Admin Tools

#32579 Database Table Crashing for

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by on Sunday, 29 March 2020 17:17 CDT

[email protected]
I am having a problem with my Virtual Private Server at a hosting company with mySQL crashing. It will basically randomly crash usually once or twice a day and restarts 5 minutes later. I spoke to the hosting company several times after performing checks, repairs, optimization on the database which does not seem to stop the issue. They keep telling me it's because of the table but I am unsure.

I am receiving the following error on the database ( i have xxxxx the database name and domain references):


Log Messages

2020-02-27 20:07:51 38 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_ipautobanhistory' is marked as crashed and should be repaired
2020-02-27 20:07:41 22 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_log' is marked as crashed and should be repaired
2020-02-27 20:07:27 8 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_storage' is marked as crashed and should be repaired
2020-02-27 20:07:27 10 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_storage' is marked as crashed and should be repaired
2020-02-27 20:07:27 11 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_storage' is marked as crashed and should be repaired
2020-02-27 20:07:25 0 [Note] /usr/sbin/mysqld: ready for connections.
2020-02-27 19:21:47 9 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_storage' is marked as crashed and should be repaired
2020-02-27 19:21:33 0 [Note] /usr/sbin/mysqld: ready for connections.
2020-02-27 19:11:49 398 [ERROR] mysqld: Table './xxxxxxx_xxxxxxxxx/dbps_admintools_log' is marked as crashed and should be repaired
2020-02-27 18:29:27 0 [Note] /usr/sbin/mysqld: ready for connections.

Memory Information

Used

2.21 GB

Available

740 MB

Installed

1.5 GB

Load Information

3.52 3.76 2.68

Uptime

36 days, 6 hours, 52 minutes, and 37 seconds

IOStat Information

avg-cpu: %user %nice %system %iowait %steal %idle 1.43 0.00 0.30 0.21 0.00 98.06 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn

Top Processes

PID

Owner

CPU %

Memory %

Command

13762

mysql

53.95

21.73

/usr/sbin/mysqld

14056

xxxxxxx

30.95

2.96

php-fpm: pool xxxxxxxx

14100

xxxxxxxx

25.06

3.09

php-fpm: pool xxxxxxxxx

14045

d1ff695

17.03

3.45

php-fpm: pxxxxxxxxxx

14037

xxxxxxxx

3.52

3.74

nicholas
Akeeba Staff
Manager
The log and ipautobanhistory tables do get quite a bit of activity since they keep a log of security exceptions and automatically banned IPs respectively. However, it is NOT normal for the table to crash. If the tables keep crashing it's an indication of a deeper issue with the database server.

I'd like to point out add that the MySQL server crash is not the result of the corrupt table but the cause of it. Your host has got it backwards.

Seeing how the MySQL server is using up 53.95% of CPU and 21.73% of memory (and its other instance 30.95$ CPU and 2.96% memory) troubles me. Together with the load information (you are running at 2.68 long term and over 3.6 short-term) it tells me the story of a database server that's quite overwhelmed. This is something the host needs to address.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!