Scan Stops after “forking”

  • Bushboy

    (@bushboy)


    9 years, 5 months ago

    Scan stops consistently ….at “forking”. I read the article by WF on this issue but I’m not comfortable messing around at that level! I’d appreciate any help to get this issuefixed!!

    This is the Detailed Scan Activity Report..

    ….
    Calling fork() from wordfenceHash with maxExecTime: 15
    [Jan 11 11:52:20] Entered fork()
    [Jan 11 11:52:21] Calling startScan(true)
    [Jan 11 11:52:21] Got value from wf config maxExecutionTime: 15
    [Jan 11 11:52:21] getMaxExecutionTime() returning config value: 15
    [Jan 11 11:52:34] 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 13003 milliseconds with 0 bytes received’, ), ), ‘error_data’ => array ( ), ))
    [Jan 11 11:52:34] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.topdogmediallc.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&cronKey=1ccb02b7154a0d626e5887d8
    [Jan 11 11:52:35] Scan process ended after forking.

The topic ‘Scan Stops after “forking”’ is closed to new replies.