WFMattR on "[Plugin: Wordfence Security] Scan can't continue - stored data not found after a fork. Got type: boolean"

Hi guys

Wordfence has worked pefectly on http://www.broughtonschoolofmotoring.com for a long while.

But now, I get this message: Scan can't continue - stored data not found after a fork. Got type: boolean

Wordfence still works on my other sites.

Any suggestions?

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

Have you updated WF to 6.1.4? That was a bug that was fixed in the latest update, at least I have just run a scan and that problem seems to have gone away.

I have the same problem as you, Steve. I have updated to WF 6.1.4 and I am still getting:

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

on scans on a site I look after at: aldeburghparishchurch.org.uk

Works fine on my other site.

Hi,

If you've both updated to 6.1.4 already, can you try running a scan manually and see if the message still occurs?

The message will still show in the "Live activity" line at the top of Wordfence pages until it's replaced by another message, so the message from the last scan before the update could still be shown.

-Matt R

Hi Matt,

Thanks for looking at this.

Yes, I've tried several manual scans and it still does it. I updated WP today but it was already showing this in the live activity, with yesterday's date, so probably not related to the WP update. My other site also has the latest WP and works fine with WF.

If it helps, last few lines in the live activity are:

[Apr 21 14:06:58] Getting plugin list from WordPress
[Apr 21 14:06:58] Found 11 plugins
[Apr 21 14:06:58] Getting theme list from WordPress
[Apr 21 14:06:58] Found 1 themes
[Apr 21 14:07:13] Analyzed 100 files containing 1.26 MB of data so far
[Apr 21 14:07:17] Scan can't continue - stored data not found after a fork. Got type: boolean

Thanks!

Nick

Matt,

One thought: the previous WF version went from leaing mode to normal scanning around this time. (But then so did my other site and that's OK...)

Nick

@nickwinter: Thanks for confirming. Can you go to the new Diagnostics page on the Wordfence menu, and click the "Send Report by Email" button, and enter wftest [at] wordfence.com? There is also be a field to enter your forum useame, so I can match it to your post here when you send the report.

@stevethefootycoach: If you've also tried a scan after updating to 6.1.4 and still see the issue, please send me your diagnostic report, following the steps above as well.

-Matt R

Matt,

Report sent.

Nick

I've also sent my report.

Thanks.

I hope you can suggest a fix. Wordfence was (is) an amazing plugin.

Just tried another scan and it worked!

Not changed anything. Just hoping it doesn't stop working!

Just tried a scan and it still doesn't work!

Glad yours is working, Steve!

Hi again,

@stevethefootycoach: Let us know if it does occur again -- these are the only two cases we've heard since 6.1.4, so it doesn't look like a widespread issue so far.

@nickwinter: Can you check with your host to see if they can upgrade the version of MySQL used on your server? (We recommend doing a full backup before a database upgrade of course.) It is a rather old version and may have trouble storing the temporary data during scans. This data is larger in the current version than what it was in older versions -- normally this shouldn't be an issue, but the database client version is likely missing some bug fixes that could cause strange issues.

You might also be able to find more details in the site's error log, or the host may find details in mysql's logs.

-Matt R