Scan fails instantly – Scan process ended after forking

  • Resolved Fixed.net

    (@fixednet)


    2 years, 7 months ago

    Hi there,

    We’re having an issue with running a scan, it fails instantly so it’s not a process timeout (but tested with higher PHP values too).

    The scan log ends with:

    [Apr 11 03:59:59:1649645999.626664:4:info] Scan process ended after forking.
    [Apr 11 03:59:59:1649645999.129222:4:info] Starting cron with normal ajax at URL <siteurl>

    And if we have the “Start all scans remotely” from Diagnostics enabled, ends with:

    [Apr 11 02:42:36:1649641356.116405:4:info] Scan process ended after forking.
    [Apr 11 02:42:35:1649641355.189022:4:info] Starting cron via proxy at URL <siteurl>

    – When doing a curl to URLs from the server, it’s 200 OK.
    – Nothing in the logs (with debug ON)
    – All plugins except WF are disabled and using default theme, replaced WP core files. (checksum is OK)
    – Files permissions and ownership are OK
    – Using the default .htaccess and no additional ones in wp-admin or elsewhere.
    – No CloudFlare
    – SSL is OK
    – Tested fully re-installing WF, including fresh DB tables with WF Assistant.
    – Have tested everything from here:
    https://www.wordfence.com/help/scan/troubleshooting/?utm_source=plugin&utm_medium=pluginUI&utm_campaign=docsIcon#if-your-scans-arent-starting
    – And also whitelisted the IPs.
    – Tested all the options for “How does Wordfence get IPs”
    – Cron is OK
    – Default wp-config
    – The Diagnostics checks are all showing green OK.

    The site was staged on a different server and having the same issue.

    Any insight would be appreciated, can provide more details or access if necessary.

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

    (@wfpeter)

    Hi @fixednet, thanks for reaching out to us.

    It certainly looks like you’ve been thorough with your scan and settings checks. Just so I can confirm some of the above information, could you send us a copy of the diagnostics page you’ve taken a look at?

    You can send one to wftest @ wordfence . com by finding the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Peter.

    Thread Starter Fixed.net

    (@fixednet)

    Hello,

    Thank you for your reply. We have now sent you 2 reports, one from the live site and one from the staging site. Please check them and let us know if we need to provide you with any additional information.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @fixednet, thanks for sending that over.

    The only possible hint to a connectivity issue would be that 38 cron jobs were overdue when the diagnostic was sent but you do mention that these were working. I’m also able to see connectivity, permissions and IP detection seem fine.

    When you mention Whitelisting IPs, did you need to do this in an external load balancer or firewall, and also was this your own server IP, Wordfence IPs or all of those? If you need our IPs, they are available here: https://www.wordfence.com/help/advanced/#servers-and-ip-addresses

    There are a some other settings that you can check, too. Your WP_MEMORY_LIMIT should be set to 128M or 256M in wp-config.php whereas it’s telling me in your diagnostics report that this is 40M at the moment. WooCommerce (as a common example) recommend 64M minimum, so if you have many hits on the site at once especially during a scan, a lower limit here could be reached fairly easily.

    For a screenshot of my recommended Performance setting options – Click Here.

    You could also set max_execution_time = 60 in php.ini. Wordfence’s scan only ever attempts to use half of this value by default but I have seen values above 60 (such as 180 or 120 in your case) causing problems before.

    Thanks,

    Peter.

    Thread Starter Fixed.net

    (@fixednet)

    Hi Peter, thanks for this!

    We tried the above tweaks but not luck unfortunately.

    Is there a way to provide WP & SSH access privately for you to check, just in case we’re missing something ?

    Thank you,
    Fixed.net

    Thread Starter Fixed.net

    (@fixednet)

    Hi Peter,

    Could we please have an update on the above ?

    Thank you,
    Fixed.net

    Plugin Support wfpeter

    (@wfpeter)

    Hi @fixednet,

    If this is still an issue now that Wordfence version has changed, could you send me another diagnostic report please using the original instructions from earlier in this topic? I was unable to find clear connectivity, IP detection, or general server configuration issues in your original diagnostic that point to scan issues with our other customers. However, I would like to see whether anything has changed between then and now that might be significant to flagging the source of why scans won’t even try to start.

    Apologies that there has been a delay, I took some extended periods of annual leave in the last month.

    Thanks again,

    Peter.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Scan fails instantly – Scan process ended after forking’ is closed to new replies.