Scan Engine Error
-
Seeing this for aa week or so now –
Scan Engine Error: Wordfence could not start a scan because the cron key does not match the saved key. (and a number)
Not sure what it means .. or what I should do.
-
Can you try this?
- Set “Maximum execution time for each scan stage” to 15
- Check the box to “Disable config caching”
- Check the box to “Enable debugging mode”
- Save the options page.
- Start a new scan (this may take a while so give it plenty of time to run)
- Copy the last 10 lines or so of the activity log and paste them here
tim
Thank you Tim – doing it now..
bcr8tive~
[Jan 24 06:59:41] Scanning: /home/content/02/13608602/html/bcr8tive/wp-content/uploads/2014/04/Armani-Prive-ss-2014-hc-039-332×996.jpg (Mem:16.0M)
[Jan 24 06:59:41] Calling fork() from wordfenceHash::processFile with maxExecTime: 15
[Jan 24 06:59:41] Entered fork()
[Jan 24 06:59:42] Calling startScan(true)
[Jan 24 06:59:42] Got value from wf config maxExecutionTime: 15
[Jan 24 06:59:42] getMaxExecutionTime() returning config value: 15
[Jan 24 06:59:43] gzinflate(): data error (2) File: /home/content/02/13608602/html/bcr8tive/wp-includes/class-wp-http-encoding.php Line: 58
[Jan 24 06:59:43] Test result of scan start URL fetch: array ( ‘headers’ => array ( ‘date’ => ‘Sun, 24 Jan 2016 11:59:42 GMT’, ‘server’ => ‘Apache’, ‘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’, ‘pragma’ => ‘no-cache’, ‘x-frame-options’ => ‘SAMEORIGIN’, ‘set-cookie’ => ‘wfvt_501525393=56a4bcafb5905; expires=Sun, 24-Jan-2016 12:29:43 GMT; path=/; httponly’, ‘vary’ => ‘Accept-Encoding’, ‘content-encoding’ => ‘gzip’, ‘content-length’ => ’32’, ‘connection’ => ‘close’, ‘content-type’ => ‘text/html; charset=UTF-8’, ), ‘body’ => ‘WFSCANTESTOK’, ‘response’ => array ( ‘code’ => 200, ‘message’ => ‘OK’, ), ‘cookies’ => array ( 0 => WP_Http_Cookie::__set_state(array( ‘name’ => ‘wfvt_501525393’, ‘value’ => ’56a4bcafb5905′, ‘expires’ => 1453638583, ‘path’ => ‘/’, ‘d
[Jan 24 06:59:43] Starting cron with normal ajax at URL http://bcr8tive.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&cronKey=2d800ade430118355f87c4c4
[Jan 24 06:59:45] Scan engine received request.
[Jan 24 06:59:45] Checking cronkey
[Jan 24 06:59:45] Fetching stored cronkey for comparison.
[Jan 24 06:59:45] Exploding stored cronkey
[Jan 24 06:59:45] Checking saved cronkey against cronkey param
[Jan 24 06:59:45] Becoming admin for scan
[Jan 24 06:59:45] Scan will run as admin user ‘*********’ with ID ‘7’ sourced from: singlesite get_users() function
[Jan 24 06:59:45] Scan authentication complete.
[Jan 24 06:59:45] Done become admin
[Jan 24 06:59:45] Requesting max memory
[Jan 24 06:59:45] Setting up error handling environment
[Jan 24 06:59:45] Setting up scanRunning and starting scan
[Jan 24 06:59:46] Got a true deserialized value back from ‘wfsd_engine’ with type: object
[Jan 24 06:59:46] Scan terminated with error: Wordfence file scanner detected a possible infinite loop. Exiting on file: wp-content/uploads/2014/04/Armani-Prive-ss-2014-hc-039-432×432.jpg
[Jan 24 06:59:46] Scan process ended after forking.
[Jan 24 15:38:07] Calling Wordfence API v2.20:https://noc1.wordfence.com//v2.20/?v=4.4.1&s=http%3A%2F%2Fbcr8tive.com&k=f0ba442a87c2a3101be699218e1d7dc737d711a3db753a8dfb8e3b6fc59b17914b1dd49fabdd42311dde5b4498c554250b801c49569c2f0853d15564c4445287&openssl=268435459&phpv=5.4.19&action=verify_googlebot&ip=107.191.102.245
[Jan 24 15:38:08] Blocking fake Googlebot at IP 107.191.102.245Does it get any farther than that?
Set the memory limit on the options page to 256m.
tim
Do you mean does it get any farther than 2014/?
I’m not sure, it seemed to have run quite a bit & I ran it all night – when I got back into the site that’s what was there and I pulled the last lines as you asked. I also tried to click “View activity log” but all I get is a blank page.
Memory limit is already set to 256.
I ran the “Test your WordPress host’s available memory”
Below:
Wordfence Memory benchmarking utility version 6.0.23.
This utility tests if your WordPress host respects the maximum memory configured
in their php.ini file, or if they are using other methods to limit your access to memory.–Starting test–
Current maximum memory configured in php.ini: 128 M
Current memory usage: 8.00M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
Completing test after benchmarking up to 80.25 megabytes.
–Test complete.–Congratulations, your web host allows you to use at least 80.25 megabytes of memory for each PHP process hosting your WordPress site.
The next scan you run, if you go do other things online or switch tabs, try refreshing the screen and seeing if it is progressing. Top reduce load we stop updating the scan log that you see and a refresh fetches the current state and tells you where it is. If the images are hanging the scan up, they should appear in the “Exclude files from scan that match these wildcard patterns” on the options page. Anything here should be examined to see if the file sizes are big (php has a limit to how big the files are which could cause the scan to fail) or if it may be a bogus image (something an attacker uploaded that has code inside it).
Let us know what you find.
tim
I disabled scan theme/plugins and have been running it again, SO FAR without issues.
Also – “Top reduce load we stop” – I don’t know what this means – but refresh the page and keep checking and so far, so good.
With that said, the site is 4 years old & my theme creates duplicate image files for mobility, so there are TONS of images. (the site is image intensive, it’s ALL about images…)
I also always compress my images in Photoshop PRIOR to uploading them but I also just recently optimized/compressed them all to reduce them per Google’s page speed recommendation. So I think it’ safe to say “I” don’t have an overly large image (and certainly it would have presented itself in the last 4 years of scanning with Wordfence?)
Which leads me to THESE questions – How would anyone upload anything to my site? No administrators but me & no login attempts – I’ve managed, with WF and other efforts to prevent all of that login attempt bull – they finally gave up AND I have over 15G of image files. Don’t think I would be able to suss out an extraneous image in 153,000 files. (eyes bugging out here)….
Do you mean that I should Exclude file paths from 4 years (12 months per) of image uploads in WF exclusion section? (Jaw drop)
PS: I’m not sure if there’s a difference Tim, but I backup the site to more than one place and I scanned with my AV, and no issues reported on the files or the database.
Also, since you raised the issue, I’m removing all of the add_images that WordPress and my theme created – it will be a bit before I’m done, but I’ll have a better handle on what is in all of my directories then.
In the meanwhile, the scan is still working without any errors.
- The topic ‘Scan Engine Error’ is closed to new replies.
