Scan Time Limit Exceeded 2

  • Wordfence: 7.11.7
    WordPress: 6.7.1
    Linux Server running Apache and FPM-FCGI.
    PHP memory_limit: 2048M
    PHP max_execution_time: 600
    PHP version: 8.3.8
    WP_MEMORY_LIMIT = 40M
    WP_MAX_MEMORY_LIMIT = 2048M

    Below is the tail-end of the log before it just died:

    [Nov 21 12:23:32] Scanning contents: wp-content/plugins/updraftplus/vendor/yahnis-elsts/plugin-update-checker/Puc/v4p13/Vcs/GitHubApi.php (Size: 12.93 KB Mem: 34 MB)
    [Nov 21 12:23:32] Scanning contents: wp-content/plugins/elementor-pro/modules/floating-buttons/classes/render/contact-buttons-var-3-render.php (Size: 9.38 KB Mem: 34 MB)
    [Nov 21 12:23:32] Scanning contents: wp-content/plugins/updraftplus/vendor/rackspace/php-opencloud/lib/OpenCloud/ObjectStore/Upload/ContainerMigration.php (Size: 5.57 KB Mem: 34 MB)
    [Nov 21 12:23:33] Forking during malware scan (10119) to ensure continuity.
    [Nov 21 12:23:33] Entered fork()
    [Nov 21 12:23:33] Calling startScan(true)
    [Nov 21 12:23:33] Got value from wf config maxExecutionTime: 20
    [Nov 21 12:23:33] getMaxExecutionTime() returning config value: 20
    [Nov 21 12:23:33] Cached result for scan start test: true
    [Nov 21 12:23:33] Starting cron with normal ajax at URL https://example.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=b4845118a3…594&signature=ab4e8834d04b…c1dec4
    [Nov 21 12:23:34] Scan process ended after forking.

    I’m revisiting this as it’s been about a month since I made some changes and wanted to see how it affected things. I went through and changed all our sites from high sensitivity to normal. This knocked down the issue about 60% but we still have quite a few still failing to scan.

    I had previously worked with @wfmargaret and tried a few suggestions they had. I set “Maximum execution time for each scan stage” to 20 and it still fails. I’m testing with a site that is very small, maybe 10 pages and 20 posts, altogether the site is only 300mb in size. Yet wordfence still is unable to complete it’s scan on the site. The last suggestion wfmargaret had was regarding a reverse proxy or a CDN. But when i reached out to Nexcess they checked logs and were unable to find anything.

    So at this point I’m kinda stuck as no one can see anything in the logs and we continue to have issues with wordfence. I sent off the diagnostic report along with the scan activity log, so you should be able to see some details. If you need anything more please let me know.

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @gmariani405, thanks for getting back in touch with us.

    I’ve spoken to Margaret, and she’s shown me the diagnostics/error/access log you sent over from that time.?I think it would be appropriate to get an updated access log and activity log now that some time has passed. I’m glad things have improved somewhat, but every scan hit recorded in the previous access log gave a 200 response. The one that failed after forking shown above didn’t seem to be there, or wasn’t reflecting errors in the logs at that time to coincide with the scan failures.

    Feel free to also send a fresh copy of its diagnostics (also to reflect any changes made in the last month) to wftest @ wordfence . com as before, using your forum username so we can identify the emails. Please also include your username in the subject of any separate emails you send containing your error logs and let us know here once you’ve sent them.

    Many thanks,
    Peter.

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