Symptoms
When the cPHulk database has crashed or a table has been marked as crashed, the MySQL error log, as well as cPHulkd logs, continue to increase in disk usage, as well as receiving notifications for cPanel regarding checkmysql. You'll notice errors that indicate the table or database has crashed in the cPHulk error log file, and database log.
Procedure.
If your installation is still utilizing MySQL for cPHulk, it is recommended to convert to SQLite to help prevent these database crashes. This is automatically done when upgraded to cPanel version 66 or higher. Grep the following from the database log, and cPanel cPHulk log.
-
grep "marked as crashed" /usr/local/cpanel/logs/cphulkd_errors.log
-
grep "marked as crashed" /var/lib/mysql/$hostname.err
Please note, your database log may be different. Please refer to the additional resources section to determine your database server log location.
If you see anything similar to this, you'll want to run the workaround below.
warn [cphulkd] 13650 DBD::mysql::db do failed: Table './cphulkd/login_track'
is marked as crashed and should be repaired at /usr/local/cpanel/Cpanel/Hulkd.pm line 435, <$client_socket> line 3.
Cpanel::Hulkd::_write_log(Cpanel::Hulkd=HASH(0x86d85b8), "errlog", "warn", "DBD::mysql::db do failed: Table
'./cphulkd/login_track' is ma"..., Cpanel::DBI::Mysql::db=HASH(0x8dd8000), undef) called at
/usr/local/cpanel/Cpanel/Hulkd.pm line 465 Cpanel::Hulkd::warn(Cpanel::Hulkd=HASH(0x86d85b8),
"DBD::mysql::db do failed: Table './cphulkd/login_track' is ma"..., Cpanel::DBI::Mysql::db=HASH(0x8dd8000),
undef) called at /usr/local/cpanel/Cpanel/Hulkd.pm line 406
Workaround
If upgrading is not an option at this time, you can rebuild the cPhulkd database:
-
/usr/local/cpanel/bin/hulkdsetup --force
-
/usr/local/cpanel/bin/cphulk_pam_ctl --enable
Comments
0 comments
Article is closed for comments.