Scans get hung-up at 48%

  • On localhost development website all scans are getting stuck at 48%. At first I thought it was a conflicting plugin and/or its files so I noted and removed the plugin directory where the scan got hung up. But all subsequent scans keep getting hung up at the same point which is reported as 48% complete. I even tried to let it run overnight last evenign and when checking in this morning it was stuck at the same place.

    No log activity and wpdebug doesn’t report anything. Version is current: 4.17.58

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Billie Mead

    (@codexdev)

    Ahh.. okay. Getting somewhere (maybe).

    Console reports:

    VM3218 admin.php:1 GET https://xxxxxxx.com/wp-admin/admin.php?page=GOTMLS-settings&scan_type=Quick+Scan&scan_only%5B0%5D=wp-content%2Fplugins&GOTMLS_mt=210468ff42f76b2d90cae9fa51ef2606 200 (OK)

    Does this provide any insight as to where to start looking to try and resolve?

    Thanks!

    • This reply was modified 6 years, 9 months ago by Billie Mead.
    Plugin Author Eli

    (@scheeeli)

    When the Quick Scan gets stuck before finishing it is usually because the memory_limit is too small. Try increasing your memory_limit in your php.ini file to see if that helps.

    Also, the Complete Scan will certainly work and do a much more thorough scan too.

    Thread Starter Billie Mead

    (@codexdev)

    Thanks for such a quick reply.

    php.ini

    memory_limit = 2048M

    wp-config: 

    define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

    Will try a Complete Scan and then next will do a shutdown and restart of everything and take it from there. This is one installation out of dozens, maybe hundreds still active with old clients and I’ve never had a single problem EVER so I’m curious what is so different here.

    Thank you again and will update as soon as its solved.

    Plugin Author Eli

    (@scheeeli)

    2048M is plenty, not sure if the define lines in your wp-config.php file override that setting though. Try changing the WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT to 512M or even 1024M as a test.

    But it might not even be a memory issue, if the Quick Scan always stops on the the same directory then there may be a file in there that cannot be read and is causing the scan to hang. That is why I wrote the Complete Scan to skip over unreadable files. You will see these unreadable files reported at the end of the Complete Scan under the “Read/Write Errors”.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Scans get hung-up at 48%’ is closed to new replies.