-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max execution time of 60 seconds exceeded in CLI #2461
Comments
@kassner can you please be more specific? |
@mazhalai To be fair, the |
@kassner thank you for clarifying. |
Thank you for pointing this issue. Internal ticket MAGETWO-47892 was created for investigation |
We've experienced this issue, too. For those who need to work past it for now until the resolution is merged, we've manually set |
@keithbentrup, @kassner I'm having some trouble reproducing this. On line app/etc/di.xml:698, we disable CSSMin's option to modify settings, so for me, changing the value there does nothing for me. Can you check what is the value of $raise_php_limits in \CSSmin::__construct? And can you please check the value of ini_get('max_execution_time') in the bin/magento file itself? |
Closing this for now, if anyone knows what I'm missing to reproduce then please re-open. |
Just to be sure... ping. |
pong @dsikkema . I expierence the same issue like @kassner when I enabled CSS minification in the backend. I did some debugging and found out that It seems to be related to the compiled DI information. |
If anybody experiences the issue, try to rerun |
@whizkid79 thank you for your investigation, when I run the compiler first I do see the same result. |
I'm seeing this on 2.0.7. "-d maximum_execution_time=0" did the trick, but that really shouldn't be necessary. Only started seeing this after enabling minification. |
I'm sorry, it the -d flag didn't work at all... I had to disable the minification in order for the command to run, or to leave it on and deploy static content several times until it was able to finish it. |
I did a grep with So, edit this file temporarily and get the value to 600 - or whatever makes it work for you - at least until someone on their devteam handles this bit weird configuration in their next release. |
@katmoon's suggestion worked for me. I re-ran deployment 6 times before it successfully completed. Next time I'll give @Rui-Carvalho's solution a go. |
Hello, When I deploy, I am getting this same error
Please help.. I changed it to 600, still getting same results. I have reran the deploy over and over again, and same results. The backend has no css or js, so I cant get into their and disable it, is there a command where I can disable the minifiy? Thanks, |
@muhupower this is not related to this issue, but with the fact that you have xdebug enabled. Please refer to http://devdocs.magento.com/guides/v2.1/install-gde/trouble/tshoot_install-issues.html fix it. |
|
I've created this pull request to resolve the problem. There were two pull requests already, but neither of them fixed the problem completely. |
@tubalmartin has merged the pull request in version v2.4.8-p6. #8959 requires this version and fixes the problem in Magento. |
BTW, since the version of cssmin is fixed in composer.json file, I suggest you update it to the latest version of Cssmin released today which is v2.4.8-p8. It's the most stable and reliable so far ;) Enjoy! |
Just to let you know guys, as the maintainer of YUI-CSS-compressor-PHP-port, that I've just released v3.0.0 which is the most stable release to date. Updating to this version is strongly recommended. |
Thanks for the heads-up! |
[performance] MAGETWO-90572: Optimize retrieving product attributes
Hi,
I got this error when running
php bin/magento setup:static-content:deploy
from the CLI. I have to run with-d max_executin_time=0
to avoid the error. This should not happen since PHP CLI hasmax_execution_time
with0
as default.IMHO, we shouldn't define the
max_execution_time
or callset_time_limit
within the code, but let the php.ini values kick in or at least define it instatic.php
.Thanks!
The text was updated successfully, but these errors were encountered: