Scan Stops Unexpectedly

Is this in a shared hosting environment at all? 10 seconds seems unusually short, however some hosting environments set time limits for how long a script can run to avoid crashed scripts consuming all the resources.

Hi @canu, thanks for reaching out to us.

From the site with the scan issues:

• Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
• Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
  Set “Maximum execution time for each scan stage” to 20 on the options page
• Click to “Save Changes”
• Go to the Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• Start a new scan
• Copy the last 20 lines or so from the Log (click the “Show Log” link) once the scan finishes and paste them in the post.

This will help me see exactly what is happening when the scan fails. If the scan is still failing after going through the above process, you could also send us a site diagnostic to wftest @ wordfence . com. You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Thanks,

Peter.

Hi @wfpeter
Thanks for your quick response.

I’ll send the scan diagnostic to your e-mail address if you don’t mind.

Thanks again…

Regards,
canu

Hi @dogwomble
It is a shared environment but I’m not sure why this scan in particular is failing all of the time.

Regards,
canu

Hi @wfpeter

I’ve sent the report, have you had a chance to review it?

Regards,
canu

Hi @wfpeter

I’ve sent the report, have you had a chance to review it?

Regards,
canu

Hi @wfpeter

I’ve sent the report, have you had a chance to review it?

Would you like me to resend it?

Regards,
canu

Hi @canu,

I have received your diagnostic and can see that there were no communication errors as seen in many scan issues. The speed at which the scan fails may have suggested a problem connecting back to your site which can be common behind firewalls, but all of those tests return “OK” results.

Could you please carry out the bullet-point steps above to set the max execution time of the scan stages and try again? You can paste the last 20 lines or so of results here which might help point to the exact issue.

Thanks again,

Peter.

Hi @wfpeter

Thanks for getting back to me.

Please see the edited extract of the Log below, with ‘website’ replacing the URL of the website:

[Sep 22 12:00:50] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=4ece91bcc49d55766902c865e3d83d4c967a2aeaa0ff8a305b2a82036ddb0805f768c847f236aa311b364a94cf0743221c2b6eb748a2fae0238b7082f10c42019ef68b99c181e1a8964feb763f46ba32&s=eyJ3cCI6IjUuOC4xIiwid2YiOiI3LjUuNSIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC93d3cuYW50aWd1YWZpc2hpbmcuY29tIiwic3NsdiI6MjY4NDM5NjQ3LCJwdiI6IjcuMy4xMiIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuNDUuMCIsImNzIjoiT3BlblNTTFwvMS4wLjFlIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNy4yNi0yOS1sb2ciLCJsYW5nIjoiIn0&betaFeed=0&action=resolve_ips
[Sep 22 12:01:12] Scan stop request received.
[Sep 22 12:01:14] Ajax request received to start scan.
[Sep 22 12:01:14] Entering start scan routine
[Sep 22 12:01:14] Got value from wf config maxExecutionTime: 20
[Sep 22 12:01:14] getMaxExecutionTime() returning config value: 20
[Sep 22 12:01:14] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.website.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=6df04ea793c9bad35f5a307e879475f0&k=4ece91bcc49d55766902c865e3d83d4c967a2aeaa0ff8a305b2a82036ddb0805f768c847f236aa311b364a94cf0743221c2b6eb748a2fae0238b7082f10c42019ef68b99c181e1a8964feb763f46ba32&ssl=1&signature=ecb5c6545347237da2b2ccc0f40c99a96548b8846375c118705c97c73d49bbb5
[Sep 22 12:01:15] Scan process ended after forking.

Any further assistance would be much appreciated.

Regards,
can

Hi @wfpeter

Have you had a chance to look at this?

Regards,
can

Hi @wfpeter

Have you had a chance to look at this?

Regards,
canu

• This reply was modified 3 years, 1 month ago by canu.

Hi @canu, I have had a chance to look into the results.

If you get the “Scan process ended after forking” message as the last line in the scan log, check and make sure that you have not blocked access to the “wp-admin” directory with a “.htaccess” file or limited access to it via another method. The key issue is around permissions of access.

If you have blocked access, make sure to allow your server’s IP address to access this directory. Also, check if you have Memcache running on your server. Memcache may have to be restarted twice in order for the object cache to remove the saved Wordfence scan cronkey.

Additional scan troubleshooting in our help documentation can also be an excellent resource to check off things you’ve already tried: https://www.wordfence.com/help/scan/troubleshooting/

Thanks again,

Peter.

Hi @wfpeter

Thank you for your help, much appreciated.

Regards,
canu