Scan can’t continue – stored data not found after a fork

I have exactly the same problem without having modified my site
—-
J’ai exactement le même problème sans avoir modifé mon site

OK, this has now happened on two other sites I manage, since updating WordFence, WordPress to 4.9.6 and various other plugins. Both are relatively complex sites using Page Builder — I’ll update some others (including some simpler ones) today and tomorrow, and report back on whether a pattern emerges.
All are on LiteSpeed servers (with .htaccess element in place).

Thanks @vladimok – anyone else finding this?

UPDATE: Like @vladimok this does not seem to necessarily be triggered by updates – on another site, I checked the logs and found that a scan had failed with this error at 5am this morning before I applied any updates ?? Attempting to re-run scan manually (after updates) has generated the same error.

Hi @wwwolf

Please go to (Wordfence > Tools => Diagnostics) and click on “Send Report by Email” button at the top of the page, you can send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.

Thanks.

Thanks – I’ve done that. Incidentally, it wasn’t from either of the previous sites I’ve commented on, but another one which is MUCH simpler with way fewer plugins. It had failed before I ran the latest series of pdates, but I updated everything and ran another scan manually (which failed) before sending the report.

A solution because it becomes painful !
————-
Une solution, car cela devient pénible !

Any news on this one? Every site I’ve checked/updated recently is now failing scan with this error ??

Thought I saw a pattern emerging – the few sites I have on Apache servers don’t seem to have this problem, but the ones on newer LiteSpeed servers (which probably use much more sophisticated load balancing) do.
However…

I tried to test this by installing a new clean WordPress on an LS server, with no content or plugins except a new WordFence install (importing identical settings from another site) and running a scan on that. Unfortunately (a) the scan does complete without the “stored data not found after a fork” error, and (b) it also generates a very large number of “Undefined index” errors, so there’s something else screwed up there… not a good test really
??

I’m getting this problem too…. as far as I can see I haven’t altered anything on the site… I updated a contact form plugin and always automatically update WordPress

@albertross and @vladimok
What server software are you running on? Are you on LiteSpeed or Apache (or something else) and are you aware of any config changes made by your host(s)? I’m starting to suspect a filesystem/server/caching issue here.
It’s not LiteSpeed Cache (I don’t think) because I’ve got that disabled on most of my sites, and scan is still breaking. But there are other levels of caching and round-robin behaviour in large-scale shared hosting environments… I’m wondering if something like that might be causing this (and therefore not especially widespread if it’s limited to a particular hosting setup).

@wfalaa
I’m guessing my logs didn’t reveal anything, or you’d have got back to me?

OK – looks like we have a solution ?? … on my host anyway, but perhaps others too. It appears to be related to upgrading from MariaDB 10.1 to MariaDB 10.2 and module changes associated with that. On the sites I had a problem with, I checked phpMyAdmin and all appear to be using MariaDB 10.2.x

To fix the problem, I did the following:
cPanel -> Select PHP version
select: mysqlnd, nd_mysqli and nd_pdo_mysql
uncheck: mysqli and pdo_mysql.

Now my scans complete without this error.

For those who want more detail, here’s a link my hosts sent me:
The MySQL native driver for PHP mysqlnd is a drop-in replacement for the MySQL Client Library libmysql for the PHP script language. For more info you can see : https://dev.mysql.com/downloads/connector/php-mysqlnd/

Good luck!

Hi @wwwolf

Thanks for updating the thread with this solution, I was gathering diagnostics reports from similar cases to this one I found on the forums and I got three of them and all of them were using MariaDB 10.2.15 which was just released on 17 May 2018. I’ve also noticed that API Extensions in “mysqlnd” section has empty value in all these reports. There might be an incompatibility issue that has come with some recent WordPress update but I’m not sure about that yet.

I’m glad the solution you mentioned worked in your case, it might be helpful to other users as well.

Thanks.

It does not work

Scan Failed
The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself

• This reply was modified 6 years, 9 months ago by vladimok.

Sorry to hear it didn’t work for you, and sounds like it has triggered a different issue – probably best to start a new thread for that.

Good luck!