WordFence has stuck when scanning

  • Resolved tokar86a

    (@tokar86a)


    8 years, 5 months ago

    Hi

    i have problem whit that WordFence scanning is stopping it search at

    Comparing core WordPress files against originals in repository
    Scanning for known malware files

    Nothing is happen

    This is the info i have get in the error log:

    [Fri Nov 06 19:13:25.331565 2015] [fcgid:warn] [pid 38142] [client 85.224.253.96:61699] mod_fcgid: read data timeout in 40 seconds, referer: http://www.myabdllife.com/wp-admin/admin.php?page=Wordfence
    [Fri Nov 06 19:13:25.331616 2015] [core:error] [pid 38142] [client 85.224.253.96:61699] End of script output before headers: admin-ajax.php, referer: http://www.myabdllife.com/wp-admin/admin.php?page=Wordfence

    This is the memory test

    –Starting test–
    Current maximum memory configured in php.ini: 512M
    Current memory usage: 42.00M
    Setting max memory to 90M.
    Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
    to determine how much memory your host allows. We have requested 90 megabytes.
    Completing test after benchmarking up to 80.25 megabytes.
    –Test complete.–

    So what should i do?

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author WFMattR

    (@wfmattr)

    8 years, 5 months ago

    It sounds like your server has a timeout amount set which may be different from the one that Wordfence can read from PHP. On the Wordfence Options page, can you try setting “Maximum execution time for each scan stage” to 15? Take note of whether it was blank or if it had another number. (Blank is the default.)

    If you get a different message in the error log, or if it still has the same problem, let me know.

    -Matt R

    Thread Starter tokar86a

    (@tokar86a)

    8 years, 5 months ago

    Now when i changed the Maximum execution time to 15 everything is working.

    And the setting was blank before i added 15.

    Plugin Author WFMattR

    (@wfmattr)

    8 years, 5 months ago

    Great, thanks for confirming that it is working for you.

    Your host must have set a shorter timeout on mod_fcgid (part of the web server) than the max_execution_time in php.ini.

    Using the 15-second limit may make your scans take a little bit longer, but should continue working if the host does not change the two timeouts.

    -Matt R

    Thread Starter tokar86a

    (@tokar86a)

    8 years, 5 months ago

    I am the host. so i can make change to this time out

    max_execution_time is set to 300

    I have dont find the settings to change the mod_fcgid time out.

    I use Cpanel whit WHM.

    Any tips on how i can change this right?

    Plugin Author WFMattR

    (@wfmattr)

    8 years, 5 months ago

    I haven’t used mod_fcgid on cPanel before, so I’m not sure where to find the settings, and I don’t see them on their support site. Changing that might require changes to the config files, using cPanel’s templates (so the changes survive cPanel updates) — cPanel support may be able to help you with that, if needed.

    I think the PHP max_execution_time is normally much lower (often 30 or 60 seconds on many hosts), so that may be the cause initial cause, but if you have an scripts that rely on it being long, I don’t want to recommend making it shorter. It’s possible some scripts are run from cron or another method that isn’t limited by the mod_fcgid timeout, so I don’t want to suggest changes that might break something else. 🙂

    If you haven’t changed the max_execution_time from the default either, it may be a problem with cPanel’s defaults when mod_fcgid is enabled, so their support staff may be able to help in that case too.

    -Matt R

    catalpha

    (@catalpha)

    8 years, 2 months ago

    I’m having the same issue – Scan does not complete. I’ve changed the “Maximum execution time for each scan stage” to 15.

    I can view the system configuration from the options page but I can’t edit the file. The “max_execution_time” is currently set at 120.

    Please advise

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WordFence has stuck when scanning’ is closed to new replies.