• Hello – Every few months I get the following issue where my WordFence DB grows in size to 1GB and i have to empty it via phpMyAdmin. This is now happening every few days. Is this a known issue and is there a resolution please? My webhost is Site Ground, perhaps a conflict with SG Optimiser plug in

    Database name: dbuitbqbwtee3k
    Table: yxf_wfhoover
    Current Usage: 1030MB

    1. It has 5,212,616 rows.
    2. It has the necessary permissions, I checked this as you advised.
    3. I can manually empty/truncate but trying to have to avoid this.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @ad902374, thanks for reaching out!

    It’s “known” in the sense that wfhoover should be truncated after a successful scan so if something is stopping that, it may keep growing. Double-check your Wordfence > Tools > Diagnostics page first, expand the “MySQL” tab and check all of your required permissions return “OK”.

    If the above doesn’t point to a problem and you’re able to run a scan with Wordfence > Tools > Diagnostics > Debugging Options > Enable debugging mode enabled, and send the full scan log to wftest @ wordfence . com with your forum username in the subject line to help us find it, we can see how much it’s using wfhoover.

    An exported txt file from your Wordfence > Tools > Diagnostics > EXPORT option after a scan has finished, but before manually clearing the table would also be great attached to the same email as above. Once you’ve obtained these, you can turn off our debug mode after the scan has finished.

    If you’re also willing to send us an export of the table after a scan has finished, we may be able to see what’s happening. Even if the table is empty, the export will show how the table was created, or if it was modified in some way.

    Thanks,
    Peter.

    Thread Starter ad902374

    (@ad902374)

    Doing that now and sending to you… many thanks!!!!!!

    Thread Starter ad902374

    (@ad902374)

    Hi all information has been shared. Looking forward to suggested next steps.

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

The topic ‘Database size issue’ is closed to new replies.