Scan Failed
-
Hi,
My scan keeps failing. It gets stuck at:
Testing wp-content/debug.log
-
Hi @jarryd192, thanks for getting in touch!
Could I see the final part of the scan log before this file fails?
- Stop the existing scan if it is still running (The “Start New Scan” button turns into a “Stop” button while the scan is running).
- Go to Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20.
- Click to “Save Changes”.
- Go to the Tools > Diagnostics page.
- In the “Debugging Options” section check the circle “Enable debugging mode”.
- If “Start scan remotely” is checked, uncheck this option.
- Click to “Save Changes”.
- Start a new scan on the Scan page.
- If the scan fails again, 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.
If the scan finishes after doing the above, you can leave all the settings above except for “Enable Debugging Mode”. For a screenshot of my recommended Performance setting options – Click Here.
Thanks,
Peter.Hi Peter, certainly,
- [Jun 18 13:27:10] Processing pending issues
- [Jun 18 13:27:10] Analyzed 18030 files containing 346.26 MB of data.
- [Jun 18 13:27:10] Testing .env
- [Jun 18 13:27:10] Testing .user.ini
- [Jun 18 13:27:10] Testing wp-config.php.bak
- [Jun 18 13:27:10] Testing wp-config.php.bak.a2
- [Jun 18 13:27:10] Testing wp-config.php.swo
- [Jun 18 13:27:10] Testing wp-config.php.save
- [Jun 18 13:27:10] Testing #wp-config.php#
- [Jun 18 13:27:10] Testing wp-config.php~
- [Jun 18 13:27:10] Testing wp-config.old
- [Jun 18 13:27:10] Testing .wp-config.php.swp
- [Jun 18 13:27:10] Testing wp-config.bak
- [Jun 18 13:27:10] Testing wp-config.save
- [Jun 18 13:27:10] Testing wp-config.php_bak
- [Jun 18 13:27:10] Testing wp-config.php.swp
- [Jun 18 13:27:10] Testing wp-config.php.old
- [Jun 18 13:27:10] Testing wp-config.php.original
- [Jun 18 13:27:10] Testing wp-config.php.orig
- [Jun 18 13:27:10] Testing wp-config.txt
- [Jun 18 13:27:10] Testing wp-config.original
- [Jun 18 13:27:10] Testing wp-config.orig
- [Jun 18 13:27:10] Testing wp-content/debug.log
It usually gets stuck here and fails.
Hi @jarryd192,
I would check via FTP or your site’s File Manager whether wp-content/debug.log is excessively large. I’ve seen memory failures after the debug.log check, but not a case it stopping with no further feedback here, so it’s definitely worth checking. You can take a backup of the log file before clearing it out if you wish.
If that doesn’t seem to help, you can send us a diagnostic to check from the Wordfence > Tools > Diagnostics menu to us at wftest @ wordfence . com. Click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.
NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email
Thanks again,
Peter.Howdy Peter,
Thanks Peter, the scan went through after deleting the debug file.
The topic ‘Scan Failed’ is closed to new replies.