I got a bit further by resetting to the default settings, but it’s still stalling. This time at “Analyzed 11400 files containing 233.91 MB of data so far”
Hi @knittingand,
It looks like a potential timeout in the middle of scanning files, so if your server uses Litespeed, adding the noabort code prevents in-progress scans terminating: https://www.wordfence.com/help/advanced/system-requirements/litespeed/
If that’s not the case, a scan log and site diagnostic should help us out:
- Go to the Wordfence > Tools > Diagnostics page
- In the “Debugging Options” section, check “Enable debugging mode”
- Click to “Save Changes”.
- CANCEL any current scan and start a NEW scan
- Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.
You can then send a diagnostic report to wftest @ wordfence . com from the top of the Wordfence Tools > Diagnostics page. Click on “Send Report by Email”.
Please add your forum username where indicated and respond here after you have sent it because the inbox is not monitored.
Many thanks,
Peter.
There wasn’t any option to add my forum username when I sent it but you’ll see it’s obvious in the logs.
I had to stop the scan when it stalled. I just had my server upgraded due to maxing out services so hopefully if they’ve put a limit on services anywhere I can change it now if necessary.
Hi @knittingand,
The activity log that you’ve sent over is different to the Scan Log and Diagnostic report so that’s why there was no username prompt. I found it though and it will likely help in conjunction with your Diagnostic, which I will still need to know a little more about your server setup.
At the top of the Wordfence Tools > Diagnostics page there’s a blue “SEND REPORT” button that opens up a short form where you can enter your username before hitting “SEND”.
Thanks again,
Peter.
Done! Thanks for the clarification.
Hi @knittingand, thank-you for sending that over.
This is an interesting one. I would say your overall settings, server setup and other factors (like quantity of installed plugins) look like scans should be completing successfully. I will say that we have historically seen scan issues on your host in the past that were resolved by them adjusting the server’s firewall configuration. It could be worth checking in with your host’s support to see if they have knowledge of why Wordfence scans might be failing.
If they have no specific known reason, I have some further ideas. I know you’ve already tried low resource scanning, but the other suggestions in conjunction with that setting might help.
Set Wordfence > All Options > Performance Options > Maximum execution time for each scan stage to a number like 15 and keep “Use low resource scanning” checked to help spread the scan out a bit more or at least keep memory usage for each hit lower. Don’t forget to save changes there after you’re done.
In addition, consider:
- Adding more cache paths (if applicable) in Wordfence > All Options > Advanced Scan Options > Exclude files from scan that match these wildcard patterns such as:
wp-content/cache/*
- Keeping Wordfence > All Options > General Options > Scan images, binary, and other files as if they were executable disabled.
- Setting an overall scan time limit in Performance Options of around 3 hours.
Let us know how you get on,
Peter.
