• Resolved laig95

    (@laig95)


    Hi I am getting this error on the wordpress site when I login in:

    ‘/.wp_wfHits’ is marked as crashed and should be repaired]
    SELECT MAX(attackLogTime) FROM wp_wfHits

    When I check the MySQL database through my client’s cpanel I am getting this:

    [.wp_wfHits] warning: Table is marked as crashed
    [.wp_wfHits] warning: 9 clients are using or haven’t closed the table properly
    [.wp_wfHits] warning: Size of datafile is: 482088 Should be: 481672
    [.wp_wfHits] error: Found 1602 keys of 1600
    [.wp_wfHits] error: Corrupt

    What should I do to repair this table? I see Repair database as an option in the MySQL databases page on the cpanel but searching this issue has led me to believe that it won’t fix it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter laig95

    (@laig95)

    It has been 4 days and the plugin is still down with this issue.

    Please advise

    Thread Starter laig95

    (@laig95)

    It has been a week since my first inquiry; I will be informing my clients to switch from this plugin in favor of some of the other options available. I will also inform my clients who have paid for your service to remove it as well.

    My apologies for the late response. The forums make it easy to miss something if it comes when there are lots of posts being made and support staff are not on.

    Have you tried repairing the database table? The other thing you can try is to check the box on the Wordfence Dashboard > Global Options page in the General Wordfence Options section where it says “Delete Wordfence tables and data on deactivation” and save the changes. Then deactivate the plugin and reactivate it. When you reactivate it all the tables will be recreated. The problem there is that you would lose all your settings but if you are using Wordfence Central and have used a template to deploy the settings you can push them back out again. Alternatively exporting the settings on the Wordfence Tools > Import/Export Options page would work too. Still, the best way would be to repair the table since it involves less work and usually, as far as we’ve been told, solves the problem.

    As to what caused the table to crash, I couldn’t tell you. The MySQL log may yield clues but in my experience this is one of those things that happens on sites from time to time. It could have been a MySQL server restart, or disk space issue, a hardware problem, or even some bug in MySQL.

    At any rate I hope this solves your issue.

    Tim

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘SELECT MAX(attackLogTime) FROM wp_wfHits’ is closed to new replies.