Scan aborted due to duration limit

  • Resolved Jonas Grumby

    (@ss_minnow)


    1 month, 3 weeks ago

    I’ve been getting this error: Scan aborted due to duration limit

    Performance Options: Maximum execution time for each scan stage is set to 10

    Should I make that a higher number? I’m battling against HostPapa to keep my resource usage down on a shared server plan.

    I also got: The scheduled event, wf_scan_monitor, failed to run.

    Is this basically the same problem?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @ss_minnow, thanks for reaching out!

    The WP Cron and scan abort look like they could be related to the same reason although we have seen similar scan problems come up between HostPapa and Wordfence scans before.

    I would first try setting?Wordfence > All Options > Scan Options > Advanced Scan Options > Use only IPv4 to start scans?and see if it makes any difference as that’s been mentioned with this host before.

    If not, in?Wordfence > Scan > Manage Scan,?locate the “Performance Options” section. Try setting “Maximum execution time for each scan stage” to numbers like 20 or 15 to see if that does help. You’ll need to stop any scans running before doing that and make sure to save changes on the page each time you change the value.

    Also make sure?max_execution_time = 60?(or less) in?php.ini?too regardless of your performance options in the plugin. Wordfence’s scan only ever attempts to use half of this value by default but we have noticed issues with values higher than 60, or when its set to 0, which is effectively “no limit”.

    Let us know how you get on,
    Peter.

    Thread Starter Jonas Grumby

    (@ss_minnow)

    Thanks Peter,

    FWIW I should have also mentioned that I’m using the free version of Wordfence and I have Basic Scan Options set to Limited Scan.

    I made the change to Use only IPv4 to start scans and I’ll see if that fixes it.

    I looked at php.ini in the root folder and there is no max_execution_time setting. I checked some of the sub-folders and didn’t see another instance of php.ini. I’ll contact HostPapa about that.

    Thread Starter Jonas Grumby

    (@ss_minnow)

    max_execution_time is set to 30 in cPanel. Hostpapa says it won’t appear in php.ini but it is set.

    I changed Maximum execution time for each scan stage from 10 to 15 and ran a scan which completed successfully, so I think this is resolved.

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.