Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter djvenja

    (@djvenja)

    Hi @wfalaa – what did you manage to determine from the report I sent to you?

    Thread Starter djvenja

    (@djvenja)

    Hi @wfalaa

    I have sent the report as requested (username included).

    Thread Starter djvenja

    (@djvenja)

    Hi @wfalaa

    Thanks for getting back to me. As mentioned in my last post, there is some confusion over the amount of memory available to WordPress as I seem to be seeing conflicting information. My host (123-Reg) have confirmed that they have assigned 512MB to my hosting platform, I have defined 512MB in wp-config.php, and this figure is reflected in my memory status plugin (which shows “Server: 512MB, WordPress: 512MB”) and any server status / PHP info pages and plugins.

    However, when I set the memory available to WordFence to anything higher than around 70MB, the WordFence memory test always fails with a memory error. With the memory set at 70MB or less, the test will pass and my scan will complete, but only with both “Scan file contents for backdoors, trojans and suspicious code” and “Scan file contents for malicious URLs” disabled.

    If I run a scan with a value higher than 70MB (I have mainly used values between 250-350MB, the scan will always fail, either with a timeout or memory error.

    The main problem here seems to be how much memory WordFence believes is assigned to WordPress. All plugins and status pages state that there is 512MB available to the server (with around 9% / 49MB in use under normal circumstances), but the WordFence memory test will fail if more than 70MB is set against “How much memory should Wordfence request when scanning”.

    Thread Starter djvenja

    (@djvenja)

    I’ve finally got a scan to complete. I discovered the WordFence memory testing tool on the Tools > Diagnostics tab. The tests show I can only request up to 70MB of memory, after which the tests fail. This is unusual as the System Config page (also accessed via the Diagnostics tab) and my memory status plugin both show that the Server and WordPress have 512MB available (I have defined the WordPress level in the wp-config file), so not sure where and why memory is being limited

    Event though scans are now completing, I’ve had to further tone down the scan options otherwise the scan always times out (no more memory errors, though). I have set “How much memory should Wordfence request when scanning” to 25MB and have unchecked both “Scan file contents for backdoors, trojans and suspicious code” and “Scan file contents for malicious URLs”. Re-enabling either of these options causes the scan to time out again, even if the memory made available is increased to 60MB/70MB.

    This isn’t ideal, but it’s better than no scan completing at all. I’ve no idea why memory is being limited to around 70MB as all settings and performance checks suggest that 512MB is available – can anyone suggest why I’m seeing memory tests fail at such a low level, yet all figures point to 512MB being avaiable?

    Thread Starter djvenja

    (@djvenja)

    I’ve updated four plugins and now I’m getting memory errors again, quite early in the process now (around about 4700 files into analysis). I’m going to give this a few more days while I await further support and will replace WordFence with a different security plugin if I am unable to overcome these errors by Wednesday.

    Thread Starter djvenja

    (@djvenja)

    @mishash – no, I still can’t scan. I’m not getting any more memory errors, just timeouts now. Have enabled debugging, but I’m not really getting any extra info (as far as I can see). With debugging enabled, the last scan timed out with the following info:

    [Apr 29 23:36:11:1525041371.976361:4:info] Scanning: /path/to/file/wp-content/plugins/updraftplus/methods/ftp.php (Mem:52.0M)[Apr 29 23:36:12:1525041372.000090:4:info] Calling fork() from wordfenceHash with maxExecTime: 96
    [Apr 29 23:36:12:1525041372.000872:4:info] Entered fork()

    Thread Starter djvenja

    (@djvenja)

    Have run another scan this morning which has failed without any specific error, except for:

    “Scan Failed
    The current scan looks like it has failed. Its last status update was 14 mins ago. You may continue to wait in case it resumes or stop and restart the scan. Some sites may need adjustments to run scans reliably.”

    Have checked the full log, but this also shows no further errors. It stopped mid-analysis this time:

    [Apr 27 08:45:52:1524815152.772402:2:info] Analyzed 4100 files containing 71.29 MB of data so far

Viewing 7 replies - 1 through 7 (of 7 total)