Wordfence scan dies

  • Resolved FireMyst

    (@firemyst)


    8 years, 1 month ago

    Hi there:

    I’ve been trying to run Wordfence scans on my WordPress site, and keep receiving the following from debug mode. Note that I’ve removed certain values and put replacements in brackets [] :

    
[Oct 10 09:20:56] Calling fork() from wordfenceHash::processFile with maxExecTime: 15
[Oct 10 09:20:56] Entered fork()
[Oct 10 09:20:56] Calling startScan(true)
[Oct 10 09:20:56] Got value from wf config maxExecutionTime: 15
[Oct 10 09:20:56] getMaxExecutionTime() returning config value: 15
[Oct 10 09:21:06] Test result of scan start URL fetch: WP_Error::__set_state(array( 'errors' => array ( 'http_request_failed' => array ( 0 => 'cURL error 28: Connection timed out after 10000 milliseconds', ), ), 'error_data' => array ( ), ))
[Oct 10 09:21:06] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/[mydomain].com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&cronKey=[removed just in case]
[Oct 10 09:21:08] Scan process ended after forking.

    I have the SSL tickbox unchecked in the Diagnostics config settings.

    Does anyone have any ideas on things to try?

    Thanks!

    • This topic was modified 8 years, 1 month ago by FireMyst. Reason: Put the logging info in a code block
Viewing 3 replies - 16 through 18 (of 18 total)
  • Thread Starter FireMyst

    (@firemyst)

    Two days later and the scan I started above is STILL GOING.

    There’s definitely some sort of bug in the WordFence scanning process because it should not be running for days on end, even if it “times out” at some point it should know to quit.

    I think you guys really need to look at this. ??

    Hi,
    If the scan is stuck at some point for an hour or so, you probably should terminate it by pressing “Click to kill the current scan.” link under “Start a Wordfence Scan” button.

    Thanks for checking “admin-ajax.php” response, we are now sure that this file isn’t blocked, so we are waiting for some clarification from your web host regarding the cURL error 28: Connection timed out issue, hopefully they can shed some lights over here.

    Thanks.

    Thread Starter FireMyst

    (@firemyst)

    Hi @wfalaa!

    We’ve discovered what the issue is. My ISP implemented a security protocol under which scripts attempting to increase the php_memory limit to 256MB or more trigger a 10 minute temporary firewall ban on connections from the IP executing the script.

    I had set the WordFence memory request limit to 256 as per WordFence’s documented recommendation. So for now I have the memory limit set at 128MB instead and it’s working perfectly.

    So for future reference, if anyone else experiences this issue, have them decrease the memory limit and wait 15 minutes before running another scan.

    Second though — I believe there should be some checks in the WordFence scan so that if a script is running continuously for more than an hour and isn’t getting anywhere, it should kill itself. It should be able to check if there’s some sort of “block” so it doesn’t continuously run and run and run indefinitely.

    Otherwise, it’s an awesome plugin. Keep up the great work and thanks for your assistance!

    This topic can be closed now.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Wordfence scan dies’ is closed to new replies.