Wordfence: Scan Failed
-
Hi, My wordfence scan is failing for 3 days. I tried setting and adjusting different parameters like max_execution_time and memory_limit with no luck. Please suggest how to fix the issue.
—– SCAN RESULT FAILURE MESSAGE —–
Scan Failed
The current scan looks like it has failed. Its last status update was 11 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.
—–
—– Wordfence Full Activity Log —–
[Apr 11 09:26:03:1523438763.699106:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.woff (Size: 58.47 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.624182:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.ttf (Size: 97.58 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.623013:2:info] Scanned contents of 43 additional files at 0.15 per second
[Apr 11 09:26:03:1523438763.407706:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.svg (Size: 182.1 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.356423:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.min.css (Size: 14.63 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.255376:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.eot (Size: 97.86 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.204876:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/typicons.css (Size: 22.08 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.161838:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/typicons/src/font/LICENCE.md (Size: 4.15 KB Mem: 30 MB)
[Apr 11 09:26:03:1523438763.149257:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/lib/isotope.css (Size: 1.23 KB Mem: 28 MB)
[Apr 11 09:26:02:1523438762.997450:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_settings.min.css (Size: 46.84 KB Mem: 28 MB)
[Apr 11 09:26:02:1523438762.950449:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_settings.css (Size: 11.25 KB Mem: 28 MB)
[Apr 11 09:26:02:1523438762.718424:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_frontend_editor_iframe.min.css (Size: 47.66 KB Mem: 28 MB)
[Apr 11 09:26:02:1523438762.552321:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_frontend_editor_iframe.css (Size: 53.66 KB Mem: 28 MB)
[Apr 11 09:26:02:1523438762.550597:2:info] Scanned contents of 33 additional files at 0.11 per second
[Apr 11 09:26:00:1523438760.159111:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_frontend_editor.min.css (Size: 193.99 KB Mem: 28 MB)
[Apr 11 09:26:00:1523438760.157150:2:info] Scanned contents of 32 additional files at 0.11 per second
[Apr 11 09:25:53:1523438753.625608:4:info] Scan process ended after forking.
[Apr 11 09:25:53:1523438753.317244:4:info] Scanning contents: wp-content/plugins/js_composer/assets/css/js_composer_frontend_editor.css (Size: 153.03 KB Mem: 26 MB)
[Apr 11 09:25:53:1523438753.311373:4:info] Got a true deserialized value back from ‘wfsd_engine’ with type: object
[Apr 11 09:25:53:1523438753.290263:4:info] Setting up scanRunning and starting scan
[Apr 11 09:25:53:1523438753.290086:4:info] Setting up error handling environment
[Apr 11 09:25:53:1523438753.289902:4:info] Requesting max memory
[Apr 11 09:25:53:1523438753.289728:4:info] Done become admin
[Apr 11 09:25:53:1523438753.289529:4:info] Scan authentication complete.
[Apr 11 09:25:53:1523438753.288680:4:info] Scan will run as admin user ‘admin’ with ID ‘1’ sourced from: singlesite get_users() function
[Apr 11 09:25:53:1523438753.287878:4:info] Becoming admin for scan
[Apr 11 09:25:53:1523438753.287535:4:info] Checking saved cronkey against cronkey param
[Apr 11 09:25:53:1523438753.287366:4:info] Exploding stored cronkey
[Apr 11 09:25:53:1523438753.287167:4:info] Fetching stored cronkey for comparison.
[Apr 11 09:25:53:1523438753.286990:4:info] Checking cronkey
[Apr 11 09:25:53:1523438753.286721:4:info] Scan engine received request.
[Apr 11 09:25:52:1523438752.620692:4:info] Starting cron with normal ajax at URL https://abc.com.au/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=94f1537259be1dc23647344
[Apr 11 09:25:52:1523438752.619861:4:info] Test result of scan start URL fetch: array ( ‘headers’ => Requests_Utility_CaseInsensitiveDictionary::__set_state(array( ‘data’ => array ( ‘date’ => ‘Wed, 11 Apr 2018 09:25:52 GMT’, ‘content-type’ => ‘text/html; charset=UTF-8’, ‘set-cookie’ => array ( 0 => ‘__cfduid=d9cd0773e1b15fa33c0036518524512cf1523438751; expires=Thu, 11-Apr-19 09:25:51 GMT; path=/; domain=.nexxa.com.au; HttpOnly’, 1 => ‘wfvt_670224425=5acdd4a08d82a; expires=Wed, 11-Apr-2018 09:55:52 GMT; Max-Age=1800; path=/; secure; HttpOnly’, ), ‘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’, ‘vary’ => ‘Accept-Encoding’, ‘expect-ct’ => ‘max-age=604800, report-uri=”https://report-uri.cloudflare.com/cdn-cgi/be
[Apr 11 09:25:51:1523438751.627461:4:info] getMaxExecutionTime() returning default of: 15
[Apr 11 09:25:51:1523438751.627194:4:info] Got max_execution_time value from ini: 0
[Apr 11 09:25:51:1523438751.626945:4:info] Got value from wf config maxExecutionTime:
[Apr 11 09:25:51:1523438751.626610:4:info] Calling startScan(true)
[Apr 11 09:25:51:1523438751.500585:4:info] Entered fork()
The topic ‘Wordfence: Scan Failed’ is closed to new replies.