Initial scan fails every time

NOTES:
Godaddy virtual Linux hosting
Nine (9) other sites scan without incident
Yesterday scans ran out of time (3 hours -> 6 hours -> now 24 hours)
Last several scans fail inexplicably after <1 hour

Hi @helices
Please kill any running scan at the moment and make sure “debug mode” is enabled then run a new scan. When it hangs, send a scan activity log to “alaa [at] wordfence [dot] com”. I’ll take a look on this report and let you know my findings.

It will be helpful also if you can send a diagnostics report from (Tools > Diagnostics) to the same email address.

Thanks.

OK

I sent the diagnostics report earlier this morning.

I just emailed the debug scan activity log minutes ago.

Please, advise. Thank you.

~ Mike

wfalaa (@wfalaa), please, verify that you have received all necessary information from me. It’s not clear that I submitted the (2) files properly.

Thank you.

~ Mike

Hi Mike,

I got only the “Scan Activity” log, if you can resend the diagnostics report that would be awesome!

After checking the scan activity log, I can see your server is running LiteSpeed, could you please follow this guide then run a new scan and recheck this issue?

Thanks.

OK

I updated .htaccess, as requested.

I turned ON debug mode.

I ran a scan that failed 15 minutes later.

I clicked [Email Activity Log] to alaa at wordfence.com

Do you have what you need?

Please, advise. Thank you.

~ Mike

• This reply was modified 6 years, 6 months ago by helices.

Please, advise status.

Thank you.

Hi @helices,
Sorry we weren’t able to get back to you sooner. Are you still experiencing this issue? It does sound to me like 200k files could be a problem, depending on how fast your server is at opening, closing and reading files. If you exclude the folder that contains those files, does the scan complete?

One problem I have discovered is that your wfHoover table is out of control!

My hosting provider disable database access earlier this week, because my database exceeded 1GB and more than 6.5 million rows. On investigation, I found that wfHoover had more than 5.5 million rows. I truncated that table to regain website functionality.

If Wordfence cannot fix this problem, I must delete the plugin.

Please, advise. Thank you.

~ Mike

Hi @helices!

The wfHoover table is normally truncated after every scan. It sounds like the database user your WordPress is running as may not have permission to truncate tables? In some versions of MySQL DROP may be required to truncate. Can you please check to make sure the database user has the necessary permissions? You should be able to see this via the Wordfence Tools > Diagnostics page in the MySQL section.

Within three (3) hours of starting the next scan, wfHoover went from zero (0) to 3.5 million rows!

I had no choice except to disable and delete Wordfence, including deleting all Mysql tables.

If you have some suggestions, I’m willing to try a new install.

~ Mike

Hi @helices,
Did you check if the database had all necessary permissions before you ran the scan? As I mentioned, you would have been able to see that on the Wordfence Tools > Diagnostics page.

Yes, it has all necessary privileges.

Thanks @helices,
I’m not quite sure then to be honest why your tables would keep growing infinitely. If are able to activate Wordfence at this point you could send me a new diagnostics report and I’d be happy to have a look to see if I can see anything that might give a hint. If so, send it to [email protected], make sure to mention your username helices so I know who it’s coming from.

Thanks!

What you seem to miss is, after I truncated wfHoover (zero rows!) the _first_ scan after that, 3+ hours into it, there were 3.5 MILLION rows in wfHoover.

Mine is no issue of _not_ cleaning up after successful scans. It could be that, too; but, if one scan, starting with empty table, gets millions of rows before completion, THAT is a problem …