Scan Stops Immediately

  • Resolved Mike V

    (@mikevens)


    2 years, 12 months ago

    My WF scans stop immediately after starting. I have tried setting the debug option to “Start Scans Remotely” but no joy. Here is my log file:

    [Dec 01 10:50:51] Ajax request received to start scan.
[Dec 01 10:50:51] Entering start scan routine
[Dec 01 10:50:51] Got value from wf config maxExecutionTime:
[Dec 01 10:50:51] Got max_execution_time value from ini: 30
[Dec 01 10:50:51] getMaxExecutionTime() returning half ini value: 15
[Dec 01 10:50:54] Test result of scan start URL fetch: array ( 'headers' => Requests_Utility_CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'server' => 'nginx', 'date' => 'Wed, 01 Dec 2021 15:50:54 GMT', 'content-type' => 'text/html; charset=UTF-8', 'vary' => 'Accept-Encoding', 'x-powered-by' => array ( 0 => 'PHP/7.3.33', 1 => 'PleskLin', ), 'x-robots-tag' => 'noindex', 'x-content-type-options' => 'nosniff', 'expires' => 'Wed, 11 Jan 1984 05:00:00 GMT', 'cache-control' => 'no-cache, must-revalidate, max-age=0', 'x-frame-options' => 'SAMEORIGIN', 'referrer-policy' => 'strict-origin-when-cross-origin', 'x-cache-php-bypass' => 'No', 'x-cache-nginx-reason' => 'No caching plugin used', 'content-encoding' => 'br', ), )), 'body' => 'WFSCANTESTOK', 'response' => array ( 'code' => 200, 'message' => 'OK', ), 'cookies' => array ( ), 'filena
[Dec 01 10:50:54] Starting cron with normal ajax at URL https://www.merrickville-bridge.ca/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=custom&cronKey=c673770a03a226dda48989244785ec15&signature=b3eaf99e91c0201a30b84e7b6e863d074f4daef31e68cf8358e0117cf2bef57e
[Dec 01 10:50:54] Scan process ended after forking.
[Dec 01 10:51:15] Scan stop request received.

    Any thoughts, please?

    Thanks.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @mikevens, thanks for getting in touch.

    It is worth, after seeing that log entry, pointing you in the direction of our Scan process ended after forking documentation to ensure permissions and .htaccess blocks are not preventing access to the wp-admin folder.

    Also, these issues can be related to caching. If you’re using Litespeed cache, WP Engine, or a plugin like Advanced Caching on your site, you could try flushing/clearing them yourself from their settings pages. Once the data has been cleared try another scan if the above documentation didn’t do the trick!

    If you take a look at your diagnostic report on Wordfence > Tools > Diagnostics page and see any communication errors or failure messages in red, click on “Send Report by Email”. Please send a copy to wftest @ wordfence . com, add your forum username where indicated and respond here after you have sent it so we can try to get to the bottom of the cause.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email`

    Let me know how you get on.

    Thanks,

    Peter.

    Thread Starter Mike V

    (@mikevens)

    Peter

    Checked and no htaccess or permission issues (all directories are 755 and file are 644).

    Report sent to your email.

    Thanks

    Mike

    Plugin Support wfpeter

    (@wfpeter)

    Hi @mikevens,

    Thanks for sending that over. Communications between your server and ours seem fine, so I’m looking at execution times and memory limits as a possible factor here.

    You could try setting max_execution_time = 60 in php.ini so that the half Wordfence’s scan attempts to use by default is 30 seconds rather than 15. Having said this, we usually recommend setting the scan inside Wordfence to 20 so it doesn’t exceed PHP’s capabilities for your server, so you could try this too:

    • Stop any 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 Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20.
    • Click to “Save Changes”.

    The WP_MEMORY_LIMIT that is set to 40M currently should be increased to 128M in wp-config.php. WooCommerce (as a common example) recommend 64M minimum, so if you have many hits on the site at once especially during a scan, this current limit of 40M could be reached fairly easily. Your PHP memory_limit value is already set high enough to accommodate this change.

    If none of the approaches above work, there are other scan troubleshooting steps you might wish to try at: https://www.wordfence.com/help/scan/troubleshooting/

    Let me know if you’ve exhausted those options, especially after trying again with and without remote scans enabled.

    Thanks,

    Peter.

    Thread Starter Mike V

    (@mikevens)

    Peter

    I’ve done all the steps suggested but no joy. The scan only lasts for one (1) second (2 at most) before terminating.

    Thanks for your help.

    Mike

    Plugin Support wfpeter

    (@wfpeter)

    Hi @mikevens,

    Has the site attempted to run an automatically scheduled scan in the last 5 days? Now that you’ve made the necessary changes highlighted above and followed our troubleshooting documentation, feel free to send us another diagnostic using the instructions I provided before so I can see if anything has changed in your configuration that may shed light on what’s happening.

    Thanks,

    Peter.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Scan Stops Immediately’ is closed to new replies.