Scan Failing
-
Hi,
I cannot seem to get the Wordfence Scan to run on my website. I am getting the following error:
Scan Failed
The current scan looks like it has failed. Its last status update was 31 mins ago. You may continue to wait in case it resumes or stop and restart the scan. Some sites may need adjustments to run scans reliably. Click here for steps you can try.I have tried to enable the “use low resource scanning” option but I am getting the same results.
How can I get the scans to run successfully?
Thanks
The page I need help with: [log in to see the link]
-
Hello @wanderingon and thanks for reaching out to us!
Can you do the following so I can get the information I need to help you?
- 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 from the Log (click the “Show Log” link) or so of the activity log and paste them in the post.
On occasion, this fixes it straight away. That’s because adding 20 for the “Maximum execution time for each scan stage” tells the scan to pause every 20 seconds and start again where it left off. If this fixes the issue and scans run again, you can leave all the settings above except for “Enable Debugging Mode”.
Thanks!
Hi @wfadam
I followed your instructions and below are the last few lines of the log.
[Oct 24 18:25:45] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/assets/js/navigation.js (Mem:44.0M)
[Oct 24 18:25:45] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/assets/js/skip-link-focus-fix.js (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/comments.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/footer.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/front-page.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/header.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/back-compat.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/color-patterns.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/custom-header.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/customizer.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/icon-functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/template-functions.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/inc/template-tags.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/index.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/page.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/search.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/searchform.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/sidebar.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/single.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/footer/footer-widgets.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/footer/site-info.php (Mem:44.0M)
[Oct 24 18:25:46] Scanning: /var/www/vhosts/127/285785/webspace/httpdocs/wanderingon.com/wp-content/updraft/themes-old/twentyseventeen/template-parts/header/header-image.php (Mem:44.0M)
[Oct 24 18:25:47] Calling fork() from wordfenceHash with maxExecTime: 20
[Oct 24 18:25:47] Entered fork()
[Oct 24 18:25:48] Calling startScan(true)
[Oct 24 18:25:48] Got value from wf config maxExecutionTime: 20
[Oct 24 18:25:48] getMaxExecutionTime() returning config value: 20
[Oct 24 18:26:06] Test result of scan start URL fetch: WP_Error::__set_state(array( ‘errors’ => array ( ‘http_request_failed’ => array ( 0 => ‘cURL error 28: Operation timed out after 18001 milliseconds with 0 bytes received’, ), ), ‘error_data’ => array ( ), ))
[Oct 24 18:26:06] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/wanderingon.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=bb7dc4f3ff826edf9800cf553fa65b1c&k=0ea4bddc8c0ebdb959d92300f0217cf36015a6e9123009839227487116b6f87a74248c9d11d123ff2c8cdbd56e6d4a2a7bdca840ba9af4ccbfa0e433158e74aecbfcaa66ef069ece9ea144c7ba4417b7&ssl=1&signature=80c4bebbbe3e8d2efcfed78c021ecda70c440f560d80435c394207d82068ffb7
[Oct 24 18:26:07] Scan process ended after forking.If you need anything else, please let me know.
Thanks,
BrianLooks like I see a cURL 28 error in there. This could be an issue with a connection back to your site. Are you using a CDN such as Cloudflare?
Can you send a diagnostic report 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!
Hi @wfadam
Yes, I am using Cloudflare CDN.
I have sent a diagnostic report using the “Send Report by Email” feature now.
If there’s anything else that I can do, please let me know.
Thanks,
BrianThanks for sending that report @wanderingon
If you check this screenshot from your diagnostic: https://prnt.sc/v737u1
It looks like you might have to reinstall your cURL. Reach out to your host to request they complete that for you. Once you have it reinstalled, try another scan, if it fails, let me know here!
Thanks again!
Tanks for the quick reply @wfadam
I contacted my hosting company recently about the MySQL errors identified in the diagnostics report. They replied to say that “None of those items listed are issues to be concerned about.” They also said that “The site is loading very quickly for me and a curl test shows:
~$ time curl -s https://wanderingon.com
real 0m0.507s
user 0m0.040s
sys 0m0.000sThat shows a load time of 0.5 seconds”
I am on a shared hosting plan. Can I reinstall the cURL myself or will the hosting company have to do it? What reason can I provide them with to highlight why this needs to be completed?
Thanks
It could be a permissions issue within your database then.
I tested your cURL and it does look likes it working but it looks like the permissions aren’t set correctly for Wordfence to write to the database.
Ask your host about the permissions in
/wp-config.php
. You can check them yourself if you would like. Verify that define(‘DB_USER’, *****) is the correct username.Let me know how this goes!
Thanks!
Hi @wfadam
I have contacted the hosting company now. I will let you know what they say.
Thanks,
BrianJust let me know how it goes!
Thanks again!
- The topic ‘Scan Failing’ is closed to new replies.