Support » Plugin: Wordfence Security - Firewall & Malware Scan » "Kill the current scan" not working

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author WFSupport

    (@wfsupport)

    My next step would be to open the javaScript Console on the scan page and see if there are any errors in red showing.

    Let me know what you see.

    tim

    No errors showing up in the console.

    It could be entirely unrelated, but I did notice that the WordPress latest version checker is not working either. I’m running 4.2 and it’s incorrectly showing as the current version (should be prompting me to upgrade to 4.2.1).

    I may manually upgrade and see if that clears anything up…

    Plugin Author WFSupport

    (@wfsupport)

    That might but I am betting there is some error preventing Wordfence from doing what it needs to. Maybe something preventing wp-admin access, a plugin conflict, something…

    Also, check the database table viewer (Wordfence options page, near bottom) and see if any tables report in need of repair.

    Do the update and see if anything shakes out.

    tim

    Will do. I’ll probably do it early tomorrow morning, and will report back. Thanks!

    OK, I tried disabling all plugins except WordFence and switching themes to twentyfifteen, and then manually updated to 4.2.1.

    Neither affected the stuck scan, still apparently trying to complete itself since April 19.

    Anything else I can try? Thanks!

    Plugin Author WFSupport

    (@wfsupport)

    What’s the domain name? Is the wp-admin folder password protected? Are you using any other security plugins, like Restricted Site Access?

    tim

    The domain is visitalpinetx.com, the wp-admin folder is not password protectd, and there are no other security plugins.

    It turned out that the wfHoover table in the database had bloated to 400+MB.

    This exceeded the size limit on my hosting and INSERT privileges had been suspended for the database user account. Accordingly, the scan would not conclude, I could not upload images to the site, and WordPress auto-updates were broken.

    To regain control of the database, I had to manually delete all the wf tables and deactivate Wordfence.

    What would cause such a huge table? What does wfHoover do, and how can it be controlled?

    Plugin Author WFSupport

    (@wfsupport)

    The wfHoover table is used to temporarily store URL’s found during a scan before we check them against the Google Safe Browsing (GSB) list of known malware and phishing URLs. This is used during a scan and in other places we check things against the GSB.

    Any of the options (I think there are three of them) that scan for URLs can be disabled if you want to see which one of them is causing the problem. I’m betting it is the comment scan. The table can be truncated and cleared but not during a scan.

    tim

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘"Kill the current scan" not working’ is closed to new replies.