Scan can't continue – stored data not found after a fork. Got type: boolean

  • Resolved stevethefootycoach

    (@stevethefootycoach)


    8 years ago

    Hi guys

    Wordfence was working perfectly until recently (a great plugin by the way!)

    Now scans ‘can’t continue – stored data not found after a fork. Got type: boolean’

    An extract from the error log is below.

    Any ideas?
    ———–

    [Apr 18 09:01:21:1460970081.165726:2:error] Scan can’t continue – stored data not found after a fork. Got type: boolean
    [Apr 18 09:01:11:1460970071.762952:2:info] Analyzed 600 files containing 67.38 MB of data so far
    [Apr 18 09:01:06:1460970066.603887:2:info] Analyzed 500 files containing 5.96 MB of data so far
    [Apr 18 09:01:06:1460970066.259513:2:info] Analyzed 400 files containing 5.4 MB of data so far
    [Apr 18 09:01:05:1460970065.767304:2:info] Analyzed 300 files containing 3.8 MB of data so far
    [Apr 18 09:01:05:1460970065.403903:2:info] Analyzed 200 files containing 2.31 MB of data so far
    [Apr 18 09:01:04:1460970064.986048:2:info] Analyzed 100 files containing 1.2 MB of data so far
    [Apr 18 09:01:04:1460970064.559222:10:info] SUM_START:Scanning for known malware files
    [Apr 18 09:01:04:1460970064.556368:10:info] SUM_START:Comparing plugins against WordPress.org originals
    [Apr 18 09:01:04:1460970064.552824:10:info] SUM_START:Comparing open source themes against WordPress.org originals
    [Apr 18 09:01:04:1460970064.548900:10:info] SUM_START:Comparing core WordPress files against originals in repository
    [Apr 18 09:01:04:1460970064.542050:10:info] SUM_ENDSUCCESS:Fetching list of known malware files from Wordfence
    [Apr 18 09:01:03:1460970063.561872:10:info] SUM_START:Fetching list of known malware files from Wordfence
    [Apr 18 09:01:03:1460970063.558172:10:info] SUM_ENDSUCCESS:Fetching core, theme and plugin file signatures from Wordfence
    [Apr 18 09:01:00:1460970060.656376:10:info] SUM_START:Fetching core, theme and plugin file signatures from Wordfence
    [Apr 18 09:01:00:1460970060.646656:2:info] Found 1 themes
    [Apr 18 09:01:00:1460970060.630013:2:info] Getting theme list from WordPress
    [Apr 18 09:01:00:1460970060.627521:2:info] Found 35 plugins
    [Apr 18 09:01:00:1460970060.626780:2:info] Getting plugin list from WordPress
    [Apr 18 09:00:59:1460970059.845748:1:info] Contacting Wordfence to initiate scan
    [Apr 18 09:00:59:1460970059.841456:10:info] SUM_ENDOK:Scanning your site for the HeartBleed vulnerability
    [Apr 18 09:00:58:1460970058.477392:10:info] SUM_START:Scanning your site for the HeartBleed vulnerability
    [Apr 18 09:00:56:1460970056.474291:10:info] SUM_PAIDONLY:Checking if your IP is generating spam is for paid members only
    [Apr 18 09:00:54:1460970054.473117:10:info] SUM_PAIDONLY:Check if your site is being Spamvertized is for paid members only
    [Apr 18 09:00:52:1460970052.472472:10:info] SUM_PAIDONLY:Remote scan of public facing site only available to paid members
    [Apr 18 09:00:52:1460970052.466414:10:info] SUM_PREP:Preparing a new scan.
    [Apr 18 09:00:49:1460970049.067767:1:info] Scheduled Wordfence scan starting at Monday 18th of April 2016 09:00:49 AM
    [Apr 18 06:39:29:1460961569.082498:10:info] SUM_KILLED:A request was received to kill the previous scan.
    [Apr 18 06:39:29:1460961569.081632:1:info] Scan kill request received.
    [Apr 17 17:36:19:1460914579.541172:1:info] Scheduled Wordfence scan starting at Sunday 17th of April 2016 05:36:19 PM

    https://wordpress.org/plugins/wordfence/

Viewing 15 replies - 1 through 15 (of 17 total)
1 2
  • Thread Starter stevethefootycoach

    (@stevethefootycoach)

    8 years ago

    And in case it helps, this is my .htaccess file:

    allow from all
    ## EXPIRES CACHING ##
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType image/jpg “access plus 1 year”
    ExpiresByType image/jpeg “access plus 1 year”
    ExpiresByType image/gif “access plus 1 year”
    ExpiresByType image/png “access plus 1 year”
    ExpiresByType text/css “access plus 1 month”
    ExpiresByType application/pdf “access plus 1 month”
    ExpiresByType text/x-javascript “access plus 1 month”
    ExpiresByType application/x-shockwave-flash “access plus 1 month”
    ExpiresByType image/x-icon “access plus 1 year”
    ExpiresDefault “access plus 2 days”
    </IfModule>
    ## EXPIRES CACHING ##

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress
    # Leverage Browser Caching Ninja — Starts here
    # Do not write anything between “Leverage Browser Caching Ninja — Starts” and “Leverage Browser Caching Ninja — Ends”
    # It will be deleted while uninstalling Leverage Browser Caching Ninja plugin
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresDefault “access plus 1 month”
    ExpiresByType image/x-icon “access plus 1 year”
    ExpiresByType image/gif “access plus 1 month”
    ExpiresByType image/png “access plus 1 month”
    ExpiresByType image/jpg “access plus 1 month”
    ExpiresByType image/jpeg “access plus 1 month”
    ExpiresByType text/css “access 1 month”
    ExpiresByType application/javascript “access plus 1 year”
    </IfModule>
    # Leverage Browser Caching Ninja — Ends here
    # Leverage Browser Caching Ninja — Starts here
    # Do not write anything between “Leverage Browser Caching Ninja — Starts” and “Leverage Browser Caching Ninja — Ends”
    # It will be deleted while uninstalling Leverage Browser Caching Ninja plugin
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresDefault “access plus 1 month”
    ExpiresByType image/x-icon “access plus 1 year”
    ExpiresByType image/gif “access plus 1 month”
    ExpiresByType image/png “access plus 1 month”
    ExpiresByType image/jpg “access plus 1 month”
    ExpiresByType image/jpeg “access plus 1 month”
    ExpiresByType text/css “access 1 month”
    ExpiresByType application/javascript “access plus 1 year”
    </IfModule>
    # Leverage Browser Caching Ninja — Ends here

    # Wordfence WAF
    <IfModule mod_suphp.c>
    suPHP_ConfigPath ‘/home/broughto/public_html/broughtonschoolofmotoring.com’
    </IfModule>
    <Files “.user.ini”>
    <IfModule mod_authz_core.c>
    Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
    Order deny,allow
    Deny from all
    </IfModule>
    </Files>

    # END Wordfence WAF

    Sjoerd_W

    (@sjoerd_w)

    8 years ago

    Same issue here

    dberch

    (@dberch)

    8 years ago

    I’m having the exact same issue as well. I’ve already tried disabling caching and upping the memory to 300. Anyone found anything that worked? WordFence is working on all my other sites… just not this one. 😛

    linuxfan

    (@linuxfan)

    8 years ago

    Indeed, most websites work, some not…

    I followed the instructions at the support page but nothing works!

    Wimgbax

    (@wimgbax)

    8 years ago

    I have the same problem with Wordfence 6.1.3 only disabling check for malicious files works.

    Going back to version Wordfence 6.1.2 also solved the problem but that is not the correct way.
    I read on this forum that problem is confirmed by Wordfence and that they are working on a solution.

    dberch

    (@dberch)

    8 years ago

    Thanks Wimgbax! Hopefully WordFence will put out an update soon and that’ll fix it. 🙂

    Thread Starter stevethefootycoach

    (@stevethefootycoach)

    8 years ago

    Going back to version 6.1.2 didn’t work for me sadly.

    tonyt57

    (@tonyt57)

    8 years ago

    Same problem will wait for the fix

    kimkhd

    (@kimkhd)

    8 years ago

    same error also

    kimkhd

    (@kimkhd)

    8 years ago

    I don’t know if this helps – but under Options, Scans to Include – by the process of elimination I have found that if the line Scan for signatures of known malicious files is UNCHECKED it will scan. If it is CHECKED it will not scan.

    And – I have been hacked and my .htaccess altered. Please help!

    osully

    (@osully)

    8 years ago

    I’m having the same problem – Scan can’t continue – stored data not found after a fork. Got type: boolean

    Things went bad about 6 days ago for me.

    Tried all the hacks from all the threads I could find. No joy. 🙁

    This issue is affecting most of my 24 sites. Different hosts, different themes, different plugins.

    Usually a great plugin, will be again I’m sure…

    ryan360

    (@ryan360)

    8 years ago

    Also having the same problem as everyone listed above. Seems like the WordFence crew has really been dropping the ball recently..

    coastalproperty

    (@coastalproperty)

    8 years ago

    Same problem after the last update

    Wimgbax

    (@wimgbax)

    8 years ago

    Additional info on this problem.
    I have websites with three different webhosting companies.
    With two webhoster I have no problem, scan works fine.

    But with one webhost I have the problem as I have reported above.

    Plugin Author WFMattR

    (@wfmattr)

    7 years, 12 months ago

    Hi,

    This was fixed in the latest version — if anyone is still having trouble with scans, please make a new post using the form at the bottom of the Wordfence forum here. (The wordpress.org forum rules ask us to keep each person’s issues separate, and it also helps us keep track of open issues, so no one gets skipped in long posts.) Thanks!

    -Matt R

Viewing 15 replies - 1 through 15 (of 17 total)
1 2
  • The topic ‘Scan can't continue – stored data not found after a fork. Got type: boolean’ is closed to new replies.