After very very large waiting…error :_

  • Resolved limondv

    (@limondv)


    11 years, 8 months ago

    In “complete” scan mode…afeter few hours…the plugin thrwos the following error:

    “Request Entity Too Large The requested resource /wp-admin/admin.php does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. “

    ?We are talking about 1.400 files infected…it′s problem of the virtual memory on my server or something similar?

    In quick scan mode the plugin says the following: “The Quick Scan was unable to finish because of a shortage of memory or a problem accessing a file. Please try using the Complete Scan, it is slower but it will handle these errors better and continue scanning the rest of the files.”

    Thanks in advance Eli !

    https://www.ads-software.com/extend/plugins/gotmls/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Eli

    (@scheeeli)

    It sounds like a limitation of your server. If you can edit your php.ini file you may be able to change those values for memory_limit and post size limits too.

    Check with your hosting provider about making these changes.

    Aloha, Eli

    Thread Starter limondv

    (@limondv)

    Hi Eli ! Thanks for your great support !!

    It′s weird because we pushed up the php.ini to the following numbers and still throwing the same error…as I said before, there are a very big list of files infected !

    memory_limit = 128Mb
    post_max_size = 31Mb
    post_max_vars = 5200
    max_execution time 150 sec.

    Plugin Author Eli

    (@scheeeli)

    That is strange. Have you checked that the value you put in the php.ini are invoked and not overridden? You can use the php function phpinfo() to check the values at run-time.

    Also, as a workaround, you could click the Automatic Repair button while the Complete scan is still running but before it find too many threats. It may take a few times through to get all clean but it may help.

    You can click Automatically Repair at any point in the scan and it will keep scanning. Then when it find more click it again, and if it hangs and you need to restart the scan there will be less threat to bog it down.

    Aloha, Eli

    Thread Starter limondv

    (@limondv)

    That is strange. Have you checked that the value you put in the php.ini are invoked and not overridden? You can use the php function phpinfo() to check the values at run-time.

    Yes all is invoked properly ! :S

    Also, as a workaround, you could click the Automatic Repair button while the Complete scan is still running but before it find too many threats. It may take a few times through to get all clean but it may help. You can click Automatically Repair at any point in the scan and it will keep scanning. Then when it find more click it again, and if it hangs and you need to restart the scan there will be less threat to bog it down.You can click Automatically Repair at any point in the scan and it will keep scanning. Then when it find more click it again, and if it hangs and you need to restart the scan there will be less threat to bog it down.

    Will try…maybe that approach can help ??

    Thread Starter limondv

    (@limondv)

    Now it seems to work !!! ??

    Always seemed a problem on our server rather than a plugin issue!

    Perhaps yesterday we were working too long during the day on the web and we was exhausted the memory before starting working with your plugin

    Thanks for your concern and time Eli !

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘After very very large waiting…error :_’ is closed to new replies.

Tags