SUM_KILLED:A request was received to stop the scan

  • Resolved sibichan

    (@sibichan)


    1 year, 7 months ago

    Scan failed always It is just fresh wp installation. no plugins installed. Getting following error when enable debug mod.

    [Apr 05 14:42:44:1680691364.819452:4:info] getMaxExecutionTime() returning config value: 20

[Apr 05 14:42:44:1680691364.819268:4:info] Got value from wf config maxExecutionTime: 20

[Apr 05 14:42:44:1680691364.817282:4:info] Entering start scan routine

[Apr 05 14:42:44:1680691364.816673:4:info] Ajax request received to start scan.

[Apr 05 14:42:39:1680691359.632416:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 05 14:42:39:1680691359.632171:1:info] Scan stop request received.

[Apr 05 14:41:04:1680691264.863908:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=timestamp

[Apr 05 14:33:59:1680690839.427615:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 05 14:33:59:1680690839.427355:1:info] Scan stop request received.

[Apr 05 14:31:48:1680690708.108197:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 05 14:31:48:1680690708.107924:1:info] Scan stop request received.

[Apr 05 14:29:50:1680690590.764903:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 05 14:29:50:1680690590.764534:1:info] Scan stop request received.

[Apr 05 14:17:27:1680689847.598026:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 05 14:17:27:1680689847.597743:1:info] Scan stop request received.

    Tried this also but not working.

    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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support wfjanet

    (@wfjanet)

    Hi@sibichan,

    Thank you for reaching out to us.

    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,

    Janet

    Thread Starter sibichan

    (@sibichan)

    Diagnostic report has been sent successfully.

    Thread Starter sibichan

    (@sibichan)

    Hello. How to fix this?

    Plugin Support wfjanet

    (@wfjanet)

    Hi@sibichan,

    I hope you’re well.

    I can’t find your diagnostic report. Can you please resend it? Be sure to add your forum username where indicated.

    Thanks,
    Janet

    Thread Starter sibichan

    (@sibichan)

    [Apr 12 11:47:30:1681285650.049461:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=resolve_ips

[Apr 12 11:47:29:1681285649.739484:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/stats.json

[Apr 12 11:46:55:1681285615.589092:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=resolve_ips

[Apr 10 13:19:30:1681118370.707947:4:info] Scan process ended after forking.

[Apr 10 13:19:29:1681118369.802428:4:info] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/demo.website.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=23c324838f06546a65ba9dba44fd5cc7&k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&ssl=1&signature=db1556661ca29a8309740cb561179cb2a28fea0adb69bde7cb34a61b7e5e8170

[Apr 10 13:19:29:1681118369.801335:4:info] Test result of scan start URL fetch: array ( 'headers' => WpOrg\Requests\Utility\CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'server' => 'nginx', 'date' => 'Mon, 10 Apr 2023 09:19:29 GMT', 'content-type' => 'text/html; charset=iso-8859-1', 'content-length' => '503', 'www-authenticate' => 'Basic realm="Restricted Content"', ), )), 'body' => '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn\'t understand how to supply the credentials required.</p> <p>Additionally, a 401 Unauthorized error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html> ', 'response' => array ( 'code' => 401, 'message' => 'Unauthorized'

[Apr 10 13:19:29:1681118369.781259:4:info] getMaxExecutionTime() returning half ini value: 15

[Apr 10 13:19:29:1681118369.781078:4:info] Got max_execution_time value from ini: 30

[Apr 10 13:19:29:1681118369.780885:4:info] Got value from wf config maxExecutionTime: 0

[Apr 10 13:19:29:1681118369.778678:4:info] Entering start scan routine

[Apr 10 13:19:29:1681118369.778066:4:info] Ajax request received to start scan.

[Apr 10 13:19:02:1681118342.782516:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=resolve_ips

[Apr 10 13:19:02:1681118342.484378:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/stats.json

[Apr 10 13:18:31:1681118311.777119:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=resolve_ips

[Apr 08 14:11:35:1680948695.428307:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&s=eyJ3cCI6IjYuMiIsIndmIjoiNy45LjIiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvZGVtby5ob3N0b25uZXQuY29tXC9hbGxvY2FycmVudGFsIiwic3NsdiI6MjY5NDg4Mzk5LCJwdiI6IjguMC4yOCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODQuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFwIiwic3YiOiJBcGFjaGUiLCJkdiI6bnVsbCwibGFuZyI6ImZyX0ZSIn0&action=plugin_vulnerability_check

[Apr 08 13:48:28:1680947308.556465:4:info] Completed checking password strength of user 'admin'

[Apr 08 13:48:28:1680947308.400372:4:info] Checking password strength of user 'admin' with ID 2 (Mem:70.5M)

[Apr 08 13:48:28:1680947308.399706:4:info] getMaxExecutionTime() returning half ini value: 15

[Apr 08 13:48:28:1680947308.399304:4:info] Got max_execution_time value from ini: 30

[Apr 08 13:48:28:1680947308.398836:4:info] Got value from wf config maxExecutionTime: 0

[Apr 08 13:42:17:1680946937.660754:10:info] SUM_KILLED:A request was received to stop the previous scan.

[Apr 08 13:42:17:1680946937.660482:1:info] Scan stop request received.

[Apr 08 13:40:58:1680946858.431383:4:info] Scan process ended after forking.

[Apr 08 13:40:57:1680946857.544568:4:info] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/demo.website.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=b1a6fe15d0b9b8f69c416d857dbd1e5b&k=6e4b89ee3c06b0d7518c1d9d034d5b9d42204443222eefa41d80fe39aae578638710a48b7eb82556dcaded375daee236e96c15027df6294ff5ce2382168fae24ae059e3eb4d2147a8227403f7a10fa50&ssl=1&signature=9b901e2e2c83ac571f865854305ff99ac5d569906c2daf0720455315d72e6a5a

[Apr 08 13:40:57:1680946857.543615:4:info] Test result of scan start URL fetch: array ( 'headers' => WpOrg\Requests\Utility\CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'server' => 'nginx', 'date' => 'Sat, 08 Apr 2023 09:40:57 GMT', 'content-type' => 'text/html; charset=iso-8859-1', 'content-length' => '503', 'www-authenticate' => 'Basic realm="Restricted Content"', ), )), 'body' => '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn\'t understand how to supply the credentials required.</p> <p>Additionally, a 401 Unauthorized error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html> ', 'response' => array ( 'code' => 401, 'message' => 'Unauthorized'
    Plugin Support wfjanet

    (@wfjanet)

    Hi @sibichan,

    From the debug log above, I see the Scan process ended after forking error. This error suggests that something is blocking access to the wp-admin directory, which contains the admin-ajax.php file Wordfence needs access to.

    Please check the instructions under Scan process ended after forking in our documentation to ensure permissions or blocks are not preventing access to the wp-admin folder. Also, ensure your server IP has access to this folder.

    Let me know how it goes. 

    Thanks, 

    Janet

    Thread Starter sibichan

    (@sibichan)

    There no block for admin – wp-admin/admin-ajax.php – got 0.

    Other wordpress site working fine in same server

    Plugin Support wfjanet

    (@wfjanet)

    Hi@sibichan,

    Thanks for getting back to us.

    I still can’t find your diagnostic report. I will need it to troubleshoot further.

    Can you send a diagnostic report to?wftest @ wordfence.com? You can find 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,
    Janet

    Thread Starter sibichan

    (@sibichan)

    Many websites have same issue. I already send the repost to mail to [email protected]

    Thread Starter sibichan

    (@sibichan)

    1.Checked by deactivating all plugins.

    2. Checked by default woocommerce theme

    3. checked by changing permalinks

    4. Checked by renaming .htacess

    But not working. Same issues on other websites also hosted in different server

    • This reply was modified 1 year, 7 months ago by sibichan.
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘SUM_KILLED:A request was received to stop the scan’ is closed to new replies.