Scan failing

(@wilhud)

I am attempting to run a scan on one of our websites and it continually fails early in the process. Here is the WordFence log result…

[Jun 22 10:31:09] Ajax request received to start scan.
[Jun 22 10:31:09] Entering start scan routine
[Jun 22 10:31:09] Got value from wf config maxExecutionTime:
[Jun 22 10:31:09] Got max_execution_time value from ini: 300
[Jun 22 10:31:09] getMaxExecutionTime() returning half ini value: 150
[Jun 22 10:31:15] Test result of scan start URL fetch: array ( 'headers' => array ( 'date' => 'Wed, 22 Jun 2016 17:31:14 GMT', 'server' => 'Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_bwlimited/1.4 PHP/5.5.31', 'x-powered-by' => 'PHP/5.5.31', 'set-cookie' => 'wfvt_2001137799=576acb637e911; expires=Wed, 22-Jun-2016 18:01:15 GMT; Max-Age=1800; path=/; httponly', 'link' => array ( 0 => '; rel="https://api.w.org/"', 1 => '; rel=shortlink', ), 'x-ua-compatible' => 'IE=edge', 'x-content-type-options' => 'nosniff', 'connection' => 'close', 'content-type' => 'text/html; charset=UTF-8', ), 'body' => ' Member Home <link rel="pingback" href="h
[Jun 22 10:31:15] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/www.**********.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&cronKey=6f5809a35c0b83646578f60b
[Jun 22 10:31:19] Scan process ended after forking.

I checked and there is no .htaccess file in the wp-admin folder to block access to that area. Also, I manually navigated to the admin-ajax.php file using both http and https options and both returned the expected zero value in the browser. I also attempted to use the ‘Start all scans remotely’ option and that did not seem to change the results.

WordPress, as well as all plugins and themes are current. Do you have any other recommendations on how I could further test this failure? The installation and scans worked fine on about 30 other websites we run on the same exact server, with a similar configuration. This is a multisite environment, but I have used WordFence on 2 other multisites and it worked fine on those setups.

Thank you,
Wil

https://wordpress.org/plugins/wordfence/

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

Thread Starter wilhud
(@wilhud)

7 years, 10 months ago

I have tried uninstalling and reinstalling the plugin. Attempted using a default WP htaccess file. Increased the memory limit. Still the same forking issue is occurring. My hosting company ran tests to make sure the wordfence server was able to communicate with the admin-ajax.php file and they were able to confirm that it was working on both port 80 and port 443. I am at a loss as to why this is failing. Any other recommendations?

Thanks,
Wil

Thread Starter wilhud
(@wilhud)

7 years, 10 months ago

I have found that if I manually run the admin-ajax.php URL provided after each failure, it appears to continue the scan process…

http://www.mydomain.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&cronKey=6f5809a35c0b83646578f60b

Does manually navigating to this URL each time the fork error is triggered lose any of the functionality of the scan? If not, then I can slowly progress through the full scan manually.

Thanks,
Wil

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

The topic ‘Scan failing’ is closed to new replies.

Tags