Scan Failed

  • Resolved qumbalar

    (@qumbalar)


    4 years, 2 months ago

    Hi,

    Scan failed and i investigated the possible reasons listed below:

    -Try starting scans remotely
    -Check plugins
    -Do not password-protect wp-admin
    -Make sure our servers are not blocked from reaching your site
    -Check the database’s tables (in regular check, i saw no problem but i found a listed problem in Wordfence, listed below)
    -Check the WordPress AJAX handler

    Then, saw these steps in forum and tried:

    – 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
    – Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log and paste them in the post.

    Pasting Results:
    [Sep 18 17:43:18:1600440198.239249:4:info] Scan process ended after forking.
    [Sep 18 17:43:17:1600440197.430623:4:info] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/kacmazcorap.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=c6635de8c086ea7b0d4b1a164bbc38d2&k=25168af93b56611bead3f60a153a7f7c31515827dc97a9b5b658f542cc16ca53d093fa0e1785b73e771e18f217cef3818a8bcfec382f3c155440f185eea9f6ad&ssl=1&signature=334a71386ab57187c438f79c1551b8cc95d5ee3b767735a19e220a7b74dcca17
    [Sep 18 17:43:17:1600440197.429762:4:info] getMaxExecutionTime() returning half ini value: 45
    [Sep 18 17:43:17:1600440197.429545:4:info] ini value of 444 is higher than value for WORDFENCE_SCAN_MAX_INI_EXECUTION_TIME (90), reducing
    [Sep 18 17:43:17:1600440197.429289:4:info] Got max_execution_time value from ini: 444
    [Sep 18 17:43:17:1600440197.429078:4:info] Got value from wf config maxExecutionTime: 0
    [Sep 18 17:43:17:1600440197.428608:4:info] Entering start scan routine
    [Sep 18 17:43:17:1600440197.427498:4:info] Ajax request received to start scan.
    [Sep 18 17:43:09:1600440189.239114:10:info] SUM_KILLED:A request was received to stop the previous scan.
    [Sep 18 17:43:09:1600440189.238642:1:info] Scan stop request received.
    [Sep 18 17:42:47:1600440167.332418:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=25168af93b56611bead3f60a153a7f7c31515827dc97a9b5b658f542cc16ca53d093fa0e1785b73e771e18f217cef3818a8bcfec382f3c155440f185eea9f6ad&s=eyJ3cCI6IjUuNS4xIiwid2YiOiI3LjQuMTEiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wva2FjbWF6Y29yYXAuY29tIiwic3NsdiI6MjY4NDQzODM5LCJwdiI6IjcuMi4zMyIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3LjYyLjAiLCJjcyI6Ik9wZW5TU0xcLzEuMC4yayIsInN2IjoiTGl0ZVNwZWVkIiwiZHYiOiIxMC4yLjMzLU1hcmlhREIifQ&betaFeed=0&action=timestamp
    [Sep 18 17:39:48:1600439988.653625:10:info] SUM_KILLED:A request was received to stop the previous scan.
    [Sep 18 17:39:48:1600439988.653060:1:info] Scan stop request received.
    [Sep 18 16:54:44:1600437284.640815:10:info] SUM_KILLED:A request was received to stop the previous scan.
    [Sep 18 16:54:44:1600437284.637905:1:info] Scan stop request received.
    [Sep 18 15:17:51:1600431471.646454:10:info] SUM_KILLED:A request was received to stop the previous scan.
    [Sep 18 15:17:51:1600431471.645998:1:info] Scan stop request received.
    [Sep 18 15:07:47:1600430867.057608:10:info] SUM_KILLED:A request was received to stop the previous scan.
    [Sep 18 15:07:47:1600430867.056024:1:info] Scan stop request received.
    [Sep 18 07:54:43:1600404883.046056:10:info] SUM_FINAL:Scan complete. You have 24 new issues to fix. See below.
    [Sep 18 07:54:43:1600404883.045818:1:info] Scan Complete. Scanned 11594 files, 25 plugins, 3 themes, 28 posts, 0 comments and 2787 URLs in 6 minutes 11 seconds.

    ***

    I have also found something like this:

    Wordfence Table Check
    Tables missing (prefix wp_, regular case): wfBlocks7, wfConfig, wfCrawlers, wfFileChanges, wfHits, wfIssues, wfPendingIssues, wfTrafficRates, wfLocs, wfLogins, wfReverseCache, wfStatus, wfHoover, wfFileMods, wfBlockedIPLog, wfSNIPCache, wfKnownFileList, wfNotifications, wfLiveTrafficHuman

    Maybe this is the reason?

    Awaiting your comments,
    Regards,
    Volkan

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

Viewing 14 replies - 31 through 44 (of 44 total)
  • Thread Starter qumbalar

    (@qumbalar)

    Of course i have tried .)
    But there is nothing changed at my side but still a failed scan.

    Thanks,

    Thread Starter qumbalar

    (@qumbalar)

    These steps followed respectively:

    1
    # BEGIN litespeed noabort
    <IfModule rewrite_module>
    RewriteEngine On
    RewriteRule .* – [E=noabort:1]
    </IfModule>
    # END litespeed noabort

    2
    # BEGIN litespeed noabort
    <IfModule Litespeed>
    RewriteEngine On
    RewriteRule .* – [E=noabort:1]
    </IfModule>
    # END litespeed noabort

    3
    # BEGIN litespeed noabort
    SetEnv noabort 1
    # END litespeed noabort

    Sorry.
    Still failed to scan.

    Plugin Support WFAdam

    (@wfadam)

    Have you checked with your hosting provider if the LiteSpeed external application abort is enabled? If it is, which specific block of htaccess code to use. Once that htaccess code is set up, could you try a new scan again with debugging mode enabled as there could be new errors. It seems we had a few errors at the start and I want to make sure we are fixing all of them correctly.

    Thanks in advance!

    Thread Starter qumbalar

    (@qumbalar)

    THey say they have enabled LiteSpeed external application abort by:
    RewriteRule .* – [E=noabort:1]

    Is that the right action?

    Plugin Support WFAdam

    (@wfadam)

    Yes, thats the correct rule.

    # BEGIN litespeed noabort
<IfModule rewrite_module>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

    to be exact.

    If this is in place, disable Start scan remotely and then try to run a scan as you would normally with debugging mode on. What are we getting now?

    Thanks again!

    Thread Starter qumbalar

    (@qumbalar)

    Well, it worked now!
    I have a complete scan.

    Wow! What a journey…
    Thank you WFAdam for patience and kind help.

    We have reached a solution at the end. Now what?
    Want me to send diagnostics?

    Plugin Support WFAdam

    (@wfadam)

    What a ride it has been! @qumbalar I am just glad we could resolve it in the end.

    If you could just for my reference, so I might be able to spot the difference from your original to now.

    If you ever have any other issues or questions, please feel free to post another topic on the forums and we would be glad to assist you!

    Thanks again for your support!

    Thread Starter qumbalar

    (@qumbalar)

    I have sent the mail regarding activity log.
    Would you please tell me then what caused this problem?

    Appreciate the effort again,
    Regards,

    Thread Starter qumbalar

    (@qumbalar)

    It still fails if the option below is ticked:
    Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible).

    Awaiting your response,

    Plugin Support WFAdam

    (@wfadam)

    Does it work with that option turned off? By default, that option should be off.

    Thanks!

    Thread Starter qumbalar

    (@qumbalar)

    Ah, i mixed up, my bad.
    Ok.
    It is working while option turned off (by default).
    So? We say we are done here?

    Plugin Support WFAdam

    (@wfadam)

    As long as the scan is working correctly, I think we are all set.

    Open another topic if you run into another issue and we’d be happy to assist you!

    Thanks again!

    Thread Starter qumbalar

    (@qumbalar)

    Have idea in this thread what caused Wordfence to stop working?
    That is my last question.

    Thanks for all the support and friendly approach.
    Best,

    Plugin Support WFAdam

    (@wfadam)

    It was the LiteSpeed code we had to add.

    The LiteSpeed web server has been known to kill or stop processes that take more than a few seconds to run. It does not stop these processes gracefully but simply kills them silently.

    Thanks again!

Viewing 14 replies - 31 through 44 (of 44 total)
  • The topic ‘Scan Failed’ is closed to new replies.