Scan stops after forking

Resolved

(@redsoftdev)

I have been able to get Wordfence scans to run on some sites that are hosted on a server but they aren’t running for every site on this server.
I have tried everything in the Support documentation and on this forum including disabling all plugins except the ones that are critical to the site’s look and function, all themes and updates have been updated but nothing helps.

To just try to get the basic options of Wordfence working on a site I changed the scan to the Limited Scan Type and I’ve turned off Wordfence’s Firewall but that hasn’t helped.
I have turned on debugging and run the scans with start all scans remotely turned on and off.

These are the results of both types of scans:

1. Start all Scans Remotely turned OFF

After a failed scan I clicked the Close button on Scan Stage Failed yellow bar and started the scan again

Scan stop request received.
Ajax request received to start scan.
Entering start scan routine
Got value from wf config maxExecutionTime: 20
getMaxExecutionTime() returning config value: 20
Test result of scan start URL fetch: array ( 'headers' => . . . 'body' => 'WFSCANTESTOK', 'response' => array ( 'code' => 200, 'message' => 'OK', ), . . . 'http_response' => WP_H
Starting cron with normal ajax at URL https://[site_url]/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=limited&cronKey=[cronKey]&signature=[signature]
Scan process ended after forking.

2. Start all Scans Remotely turned ON

After a failed scan I clicked the Close button on Scan Stage Failed yellow bar and started the scan again

Scan stop request received.
Ajax request received to start scan.
Entering start scan routine
Got value from wf config maxExecutionTime: 20
getMaxExecutionTime() returning config value: 20
Starting cron via proxy at URL https://noc1.wordfence.com/scanp/[site_url]/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=limited&cronKey=[cronKey]&k=[k]&ssl=1&signature=[signature]
Scan process ended after forking.

The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)

Plugin Support wfmargaret
(@wfmargaret)

1 year, 12 months ago

Hi @redsoftdev,

Thank you for reaching out and providing the additional information on the steps you’ve taken. Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so 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,
Margaret

Thread Starter redsoftdev
(@redsoftdev)

1 year, 12 months ago

Thank you, a diagnostic report has just been emailed

Plugin Support wfmargaret
(@wfmargaret)

1 year, 12 months ago

Hi @redsoftdev,

Thanks for sending those diagnostics! Please set max_execution_time = 60 in php.ini and your WP_MEMORY_LIMIT to 128M or 256M in wp-config.php. Yoast SEO, for example, recommends 256M minimum, so if you also have many hits on the site at once during a Wordfence scan, a lower limit here could be reached fairly easily. Your PHP memory_limit value should be set to the same or higher to accommodate this change otherwise there won’t be enough room for WordPress to use the higher value it is requesting.

You also have a few overdue cron jobs. Please ensure those are completed successfully. With WP Crontrol installed, you can delete any Wordfence-related cron jobs that currently aren’t working, then deactivate Wordfence and enable it again to repopulate the cron jobs.

Your database is also reporting that you have one crashed table that should be repaired. You can view this in Wordfence > Tools > Diagnostics > Database Tables > Comment. The crashed table isn’t related to Wordfence, but I do want to recommend you repair this. You can reach out to your host if you need assistance with the database repair.

Let me know if you continue to have issues!

Thanks,
Margaret

Thread Starter redsoftdev
(@redsoftdev)

1 year, 11 months ago

I have set max_execution_time to 60 and WP_MEMORY_LIMIT to 256M. I also repaired the crashed database table and cleared the cron jobs but I’m getting the same error message.

generosus
(@generosus)

1 year, 11 months ago

Hi @redsoftdev,

It sounds like you may have already tried this potential solution, if not, give it a spin.

Cheers!

Plugin Support wfmargaret
(@wfmargaret)

1 year, 11 months ago

Hi @redsoftdev,

Thanks for following up with us. It would help to see raw access logs from the time the scan fails to see what kind of response is happening. Please start a new scan and obtain the server access logs from around time the scan fails, as well as the last 20 lines or so of the debugging output from the scan. You can send the raw access logs to wftest @ wordfence . com. Make sure to put your forum username in the subject line and let us know here when you’ve sent them so we can take a look.

Thanks,
Margaret

Thread Starter redsoftdev
(@redsoftdev)

1 year, 11 months ago

I can’t get the server access logs. I had deleted the plugin and I reinstalled it today so there isn’t much debugging output, I’ve just sent you an email with what there is.

Plugin Support wfmargaret
(@wfmargaret)

1 year, 11 months ago

Hi @redsoftdev,

Thanks for following up. Outside of the initial troubleshooting with the database tables and overdue cron jobs, there aren’t any obvious issues from the diagnostics. Please feel free to send those again if you’d like us to review them again.

Ultimately, though, while we have seen Wordfence scans run successfully on Microsoft-IIS servers, Windows and Microsoft-IIS aren’t supported, so we may not be able to resolve this. To debug further, we would need the raw access logs, particularly for the scan fork request. In the debug output, it’s the URL on the line for “Starting cron with normal ajax at URL.” If you can enable server access logs or review using the URL listed there, please check what response you see when this URL is accessed during a scan.

Thanks,
Margaret

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Scan stops after forking’ is closed to new replies.