jackplug
Forum Replies Created
-
Hi,
Really sorry for the slooooow reply – the email notification went to my spam folder for some reason.
I tried the diagnostics report and yes, I see the php_info output at the bottom. I will send you a copy (it may not help, as it looks like we will need to contact the host about this – if not, I apologise for spamming you!)
Thanks for all your suggestions and help – I’ll post back here if we have some success!
I sent you an email with (hopefully) enough info – the subject line is Re. https://wordpress.org/support/topic/scan-problem-error-writing-value-chunk-for-wfsd_engine-error (user: jackplug). I say ‘hopefully’, because phpinfo is disabled unfortunately, so I tried to work around that using specific php functions 🙂
I have added
define('WP_MEMORY_LIMIT', '64M')to wp-config and checked the box for ‘Disabled config caching’ but the problem still exists.OK, there was one small difference: unchecked caching option, error ‘Error writing value chunk for wfsd_engine (error: )’ appears after line Analyzed 900 files containing 137.71 MB of data so far. Checked caching option, error appears after line Analyzed 1000 files containing 347.34 MB of data so far. Not sure how that information could help, though 🙂
Re. “How much memory should Wordfence request when scanning” – right now, that’s set to 300 Megabytes
The hosts only suggestion was that something has changed inside .htaccess, preventing access to the tmp directory (they suggested adding setenv and creating a new tmp directory inside the webroot, which I tried and found that it did not help – I tried this in the main .htaccess and in the .htaccess located inside the Wordfence tmp directory).
Otherwise, it seems that there could be some permissions problem with the files – which I do not understand because
a) everything worked fine initially, and
b) the directories/files were created by Wordfence under the user id/group id that it already has.As for SafeMode being a problem (as I know that it can be in some situations), I don’t understand how changing that could help, as it was set to ON during the initial installation. Could there have been some update to Wordfence since the initial install date (13th May) that could have caused the problem? It’s really weird! 🙂
UPDATE:
Perhaps I could send you a diagnostics report again, as you requested in my other problem (phpinfo works fine on this host, btw :)). Do you have a different email address that you would like me to use, or should I use the same one as on there?I found the option that causes the scan to break: Scan for signatures of known malicious files.
If I enable ALL scan options, except for Scan for signatures of known malicious files, Scan files outside your WordPress installation, and Scan images, binary, and other files as if they were executable, then everything works fine. (This was previously my default settings along with Scan for signatures of known malicious files).
Incidentally, if I include the Scan for signatures of known malicious files and Scan files outside your WordPress installation options, I get a different error:
Scan Engine Error: Wordfence could not start a scan because the cron key does not match the saved key. Saved: [someKeyValue] Sent: [someDifferentKeyValue] Current unexploded: [anotherKeyValue]
But I am not sure whether that is relevant here 🙂
I have also sent a diagnostic report to your specified email address, so perhaps that helps a little.
It’s pretty typical as far as I can see – nothing weird. If it would help, I could post a partially redacted phpinfo (via Wordfence’s system info link)
Hi, it’s a different site – didn’t think that I should ask about what seem to be separate issues in the same post (but I probably should have clarified it)