Thread Starter
sip24
(@sip24)
The only remaining assumption is that you set this execution time in the plugin, to avoid freezing of the scan. Is it possible to increase it, and how to do it?
Thread Starter
sip24
(@sip24)
I have found some more log files named like
fatal-errors-2025-04-21-a3d8f2…………7ac6b.log
They full of the errors like this:
2025-04-19T22:08:19+00:00 CRITICAL Maximum execution time of 55 seconds exceeded CONTEXT: {“error”:{“type”:1,”file”:”/home…/…../public_html/wp-content/plugins/gotmls/images/index.php”,”line”:1075},”remote-logging”:true,”backtrace”:[{“file”:”/home../…./public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php”,”line”:415,”function”:”critical”,”class”:”WC_Logger”,”type”:”->”},{“function”:”log_errors”,”class”:”WooCommerce”,”type”:”->”}]}
Plugin Author
Eli
(@scheeeli)
Yes, that 55 second timeout is set in the plugin code and for good reason. You would not want to increase that timeout limit at all and if you did it would not extend the scan at all, it would actually just slow the scan down.
If you are interested in a more technical explanation then here is how it works. The complete scan process is started in your browser window and this parent process is responsible for overseeing the scan progress. each step in the whole scan process is carried out be a child process that is started and monitored by the parent window. I am using PHP function set_time_limit to make sure that each of these individual scan jobs does not get hung up or lost by the parent process (as might happen if I were to try to scan your whole server at once). None of these individual scan jobs should take more that 15 second and usually are done in under 5 seconds, so if any of them are actually timing out at 55 second and have not returned any response to the parent process within 60 seconds then something went wrong with that child process and that part of the job is marked as incomplete and re-queued to be attempted again at the end of the scan. Under normal conditions you should see the progress bar jump forward a little bit every few seconds, and if it hangs on one or two folders for a full minute every once in a while then it should still be ok in the end, it just might take a little longer. however, if the progress bar is only updated aver 60 second and it’s moving so slowly that it looks like it will take hours to complete then there is definitely something wrong with the server and the scan is not likely to successfully complete at all.
Please let me know if that explanation helps at all, and certainly let me know more about your situation if you feel that the scan is not progressing as it should. A screenshot of the scan progress is usually very helpful if something doesn’t look right. You can also contact me directly if you want to provide and sensitive or personal info that you would rather not post on this public forum.
eli AT gotmls DOT net
