Forum Replies Created

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

    (@joecodes)

    That’s good info! Maybe you could also do a pre-check by doing a rough calculation of how much memory will be required and throw a warning if memory needs to be increased. Or at least “if scanning doesn’t complete try increasing your memory.” Glad we found it. Thanks for your help!

    Thread Starter joecodes

    (@joecodes)

    Yes, now we see the error below after the initial start and failure after a few seconds reported above. Running out of memory. We bumped memory from 128 to 256 and the scan completed. Is there a less memory intensive option? I guess I should re-enable the File Snapshot option.

    [21-Jan-2018 21:15:34 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9551882 bytes) in /…/wp-includes/class-requests.php on line 381

    Thread Starter joecodes

    (@joecodes)

    I just checked and there are no php error logs generated as we normally see on this server so it doesn’t look like there are php errors.

    Thread Starter joecodes

    (@joecodes)

    I made that change and started a new scan. After a few seconds it stops and shows last scan from a couple days ago. I saw this behavior before and thought maybe I hadn’t pressed the button. This may be a separate issue. Here is what the log looks like:

    20-Jan-18 11:48:58 INFO Scheduling a scanning process
    20-Jan-18 11:48:59 INFO Starting scanning process
    20-Jan-18 11:48:59 INFO Processing step 1 (0/10)
    20-Jan-18 11:48:59 INFO Skipping NinjaScanner files integrity check
    20-Jan-18 11:48:59 INFO Processing step 2 (0/10)
    20-Jan-18 11:49:01 INFO Building files list
    20-Jan-18 11:49:01 INFO Total files found: 73391
    20-Jan-18 11:49:01 WARN Symlinks found: 11
    20-Jan-18 11:49:01 WARN Hidden scripts found: 6
    20-Jan-18 11:49:03 INFO Processing step 3 (0/10)
    20-Jan-18 11:49:03 INFO Checking WordPress core files integrity

    Then if I run it again it seems to start properly. However, when I cancel it says there has been no scan. It seems to be confused. When I ran it a second time I let it run for around 20m before canceling. Here is the log:

    20-Jan-18 11:51:08 INFO Scheduling a scanning process
    20-Jan-18 11:51:08 INFO Starting scanning process
    20-Jan-18 11:51:08 INFO Processing step 1 (0/10)
    20-Jan-18 11:51:08 INFO Skipping NinjaScanner files integrity check
    20-Jan-18 11:51:08 INFO Processing step 2 (0/10)
    20-Jan-18 11:51:10 INFO Building files list
    20-Jan-18 11:51:10 INFO Total files found: 73390
    20-Jan-18 11:51:10 WARN Symlinks found: 11
    20-Jan-18 11:51:10 WARN Hidden scripts found: 6
    20-Jan-18 11:51:10 INFO Processing step 3 (0/10)
    20-Jan-18 11:51:10 INFO Checking WordPress core files integrity
    20-Jan-18 12:10:14 INFO Cancelling scanning process

    Thread Starter joecodes

    (@joecodes)

    No errors. Below are the last lines. Does this indicate I need to create a new snapshot?

    20-Jan-18 08:52:44 INFO Theme files integrity is O.K
    20-Jan-18 08:52:44 INFO Processing step 6 (0/10)
    20-Jan-18 08:52:44 INFO Comparing previous and current file snapshots
    20-Jan-18 08:57:06 INFO Cancelling scanning process

    Thread Starter joecodes

    (@joecodes)

    Ok, that’s good to know. I may be going off topic a little, but at this point which is the greater threat, turning off rule 310 or whitelisting this one file? They both seem bad to me.

    Thread Starter joecodes

    (@joecodes)

    Great. How about a specific rule like the following?

    if (strpos($_SERVER['SCRIPT_FILENAME'], '/foo/bar/') !== FALSE &&
      $rule == 310 ) {
       return 'ALLOW';
    }
Viewing 7 replies - 1 through 7 (of 7 total)