• Resolved IILLC

    (@iillc)


    I am noticing a huge number of errors on the database. I think this is causing my VPS to slow down. Not sure but things have gotten really slow lately.

    When running repair/optimize on DB tables I am seeing this error on nearly every wf_ table.

    75 clients are using or haven’t closed the table properly

    Number is + or – a few but I am sure this should not be happening. No other wp_ table shows these kinds of connection errors.

    How can this be resolved? I like wf but if it is going to act up I am going to have to drop it.

    Seeing this support board with all of the upgrades I am glad I have not done that at least yet! I always try to wait a few weeks before upgrading to a newer version because of all of the plugin issues that always seem to crop up.

    https://www.ads-software.com/plugins/wordfence/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi

    Hope we can help.

    Can you identify which wf tables its holding open? Are there any scans going on? Is live view enabled while you are running these operations?

    Thanks!

    tim

    Thread Starter IILLC

    (@iillc)

    Thanks for the quick response!

    There was no scans happening. Live view was not enabled. (I’m pretty sure, the Falcon Engine is on and that disables it I believe.)

    Here is the log of the tables:

    [11-Sep-2014 16:20:15] Result of table check for wp_wfBadLeechers is: OK
    [11-Sep-2014 16:20:15] WARNING: Result of table check for wp_wfBlocks is: 13 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:15] Result of table check for wp_wfBlocksAdv is: OK
    [11-Sep-2014 16:20:15] WARNING: Result of table check for wp_wfConfig is: 70 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:15] WARNING: Result of table check for wp_wfCrawlers is: 27 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:15] WARNING: Result of table check for wp_wfFileMods is: 1 client is using or hasn't closed the table properly
    [11-Sep-2014 16:20:15] WARNING: Result of table check for wp_wfHits is: 1 client is using or hasn't closed the table properly
    [11-Sep-2014 16:20:15] Result of table check for wp_wfHoover is: OK
    [11-Sep-2014 16:20:15] Result of table check for wp_wfIssues is: OK
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfLeechers is: 78 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] Result of table check for wp_wfLockedOut is: OK
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfLocs is: 4 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfLogins is: 38 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfNet404s is: 75 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfReverseCache is: 29 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfScanners is: 75 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] WARNING: Result of table check for wp_wfStatus is: 70 clients are using or haven't closed the table properly
    [11-Sep-2014 16:20:16] Result of table check for wp_wfThrottleLog is: OK
    [11-Sep-2014 16:20:16] Result of table check for wp_wfVulnScanners is: OK

    Thanks for the help!

    Plugin Author Wordfence Security

    (@mmaunder)

    This is table corruption and likely your DB crashed which is what caused this. It’s indicative of an unstable DB rather than a problem with our plugin.

    Please also check the rest of your tables, it’s likely you’ll find errors there too.

    Run a full repair on the tables with problems. Then monitor both the table integrity and when/if your DB crashes. I’m guessing you’ll notice a correlation between your DB crashing (or other issues like disk corruption or disk getting full) and table corruption.

    Regards,

    Mark.

    Thread Starter IILLC

    (@iillc)

    No other tables in the database were showing any errors. Only the tables from WordFence had these errors.

    I will keep an eye on things. Maybe it was a fluke.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WF Not Closing Connections on DB’ is closed to new replies.