Scan invariably fails since earlier today

  • Resolved bjoernkw

    (@bjoernkw)


    5 years, 10 months ago

    Since today I invariably get this message when running a scan:

    “Scan Failed
    The current scan looks like it has failed. Its last status update was 16 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. Click here for steps you can try.”

    I’ve tried the various troubleshooting and performance settings, to no avail. The debug logs don’t show anything useful either.

    Even the limited scan stops after a few minutes (with the “Malware Scan” and “Content Safety” progress indicators still showing activity) with a message such as:

    “Scanned contents of 34 additional files at 3.61 per second”

    The only thing that’s changed in my configuration is that today Wordfence suggested using new default settings regarding user privacy, which I’ve opted for.

    • This topic was modified 5 years, 10 months ago by bjoernkw.
    • This topic was modified 5 years, 10 months ago by bjoernkw. Reason: Additional information
Viewing 6 replies - 1 through 6 (of 6 total)

  • Hey @bjoernkw,

    Would you mind sharing who the site is hosting with?

    Please try these steps and let me know how it goes.

    Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)

    Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”

    Set “Maximum execution time for each scan stage” to 20 on the options page
    Click to “Save Changes”

    Go to the Tools > Diagnostics page
    In the “Debugging Options” section check the circle “Enable debugging mode”

    Click to “Save Changes”

    Start a new scan

    Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log and paste them in your support topic.

    Please let me know how it goes.

    Thanks,

    Gerald

    Thread Starter bjoernkw

    (@bjoernkw)

    The site’s https://bjoernkw.com/

    I followed the process you described. These are the last 20 lines from the log:

    [Apr 25 08:37:52] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_a8a561dc5536755f8663aaed53542be5.js (Size: 357.12 KB Mem: 73.5 MB)
    [Apr 25 08:37:53] Scanned contents of 38 additional files at 2.47 per second
    [Apr 25 08:37:53] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_ab91b8279bbce4381e8ec21642a5321c.js (Size: 310.44 KB Mem: 73.5 MB)
    [Apr 25 08:37:53] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b19e952efb1cfa538f5ba96f3873d7d5.js (Size: 137.1 KB Mem: 73.5 MB)
    [Apr 25 08:37:53] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b49d7df942103d712e3aa54333bf145d.js (Size: 337.41 KB Mem: 73.5 MB)
    [Apr 25 08:37:53] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b61c328f227c8415391b554423473653.js (Size: 308.36 KB Mem: 73.5 MB)
    [Apr 25 08:37:54] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b6c9b69bb8b0f1b3bdf7269b9ec193a2.js (Size: 339.69 KB Mem: 73.5 MB)
    [Apr 25 08:37:54] Scanned contents of 43 additional files at 2.58 per second
    [Apr 25 08:37:54] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b7f9a1fcf20e6ca7d28b4c6f1613d9fc.js (Size: 323.33 KB Mem: 73.5 MB)
    [Apr 25 08:37:54] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_b8151b23ab09d4c80416f0302051fa46.js (Size: 313.33 KB Mem: 73.5 MB)
    [Apr 25 08:37:55] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_cc2cddb38f122d27a8f050f45f14110e.js (Size: 310.6 KB Mem: 73.5 MB)
    [Apr 25 08:37:55] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_ce43475e0ea315caec8ab28071b20a00.js (Size: 340.66 KB Mem: 73.5 MB)
    [Apr 25 08:37:55] Scanned contents of 47 additional files at 2.64 per second
    [Apr 25 08:37:55] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_d4da3485e3f1801e1d89ed497c3d32c2.js (Size: 329.34 KB Mem: 73.5 MB)
    [Apr 25 08:37:55] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_d9cac7ceae8ea4bb52503314b10ee5f5.js (Size: 308.81 KB Mem: 73.5 MB)
    [Apr 25 08:37:56] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_dc479f28bd3cf2ee1ddb20651a14e0eb.js (Size: 308.4 KB Mem: 73.5 MB)
    [Apr 25 08:37:56] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_e358fa8a25dc4c835267858a95d8b0d3.js (Size: 340.76 KB Mem: 73.5 MB)
    [Apr 25 08:37:56] Scanned contents of 51 additional files at 2.70 per second
    [Apr 25 08:37:56] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_eda4a009c7822634089ccb5207a6c9e0.js (Size: 326.68 KB Mem: 73.5 MB)
    [Apr 25 08:37:56] Scanning contents: wp-content/cache/autoptimize/js/autoptimize_eef1aa451604183dc026703498c1bdfa.js (Size: 353.71 KB Mem: 73.5 MB)

    After that the scan stops responding as described before.

    • This reply was modified 5 years, 10 months ago by bjoernkw.
    Thread Starter bjoernkw

    (@bjoernkw)

    Strangely enough, that last entry from the log (wp-content/cache/autoptimize/js/autoptimize_eef1aa451604183dc026703498c1bdfa.js ) now seems to have been automatically added to the “Exclude files …” entries under “Advanced Scan Options”

    • This reply was modified 5 years, 10 months ago by bjoernkw.
    Thread Starter bjoernkw

    (@bjoernkw)

    I’ve also just had a look at the PHP error logs. There are no PHP errors related to the scan.

    Thread Starter bjoernkw

    (@bjoernkw)

    This indeed was caused by a performance issue that didn’t surface in any log. Insufficient CPU time and memory was allocated to the process.

    Hey @bjoernkw,

    Thanks for the update, and happy to hear you were able to track it down. Please let us know if anything else comes up.

    Thanks,

    Gerroald

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Scan invariably fails since earlier today’ is closed to new replies.