Closed kikmedia closed 6 years ago
Same problem with Contao Manager 1.0.0-beta13 and PHP 7.0.26 on HE Webserver Basic
So, finally I am not alone. Works on none of my machines at Hosteurope.
Same here with Contao Manager 1.0.0-beta13 and PHP 7.0.26 on HE WebPack 4 L. No workaround found so far.
same here
Same here. @aschempp if you need a testing env drop me a line on Skype.
I just analyzed the problem, and it's nothing the Contao Manager can fix right now. The message is coming from Composer, and I found this related ticket: https://github.com/composer/composer/issues/945
Apparently, the machines run out of actual memory. That means the only solution is to add more memory. And as the Composer ticket explains, that does not mean more actual memory, just adding a swap file is enough. I never understand why swap files are not available by default…
The only solution for the Manager is the Composer Cloud, but that still takes a while.
I can confirm that adding the big enough swap file worked out just fine and this error is completely gone.
How can I comprehend your method @qzminski?
I have achieved this on VPS and you can find multiple tutorials over the net on how to create a swap file on your server. If you are on shared hosting however, you should probably contact the hosting support instead.
According to a personal mail from Hosteurope, they won't configure a swap file on shared hostings (neither on 'Webpacks' nor on 'WebServers'). Furthermore, they told me that there will be new products later this year where they will provide 'a lot more RAM'. So, we have to wait for that. #sigh
Thank you @kikmedia. So let's wait.
Same here, 1.0.0-beta16 on a Debian 9 VM with 1 GB of RAM. Increased to 2 GB and updating of just the core components (no extensions installed yet) did go through. The thing I'd like to add to the discussion is that while we may not be able to fix the memory hunger of composer quickly, the handling by the contao manager should be better. In my case, I saw nothing in the console output at all and it just seemed "stuck", I reloaded the page and only then the modal popped up with the error "unable to launch a new process". Since this seems to be a rather common occurrence right now, we might want to increase the amount of info the user gets in these cases.
Today, we released version 1.0.0 stable. This version also ships with Composer Cloud that allows resolving of the dependencies on our servers. You can enable it in the hosting configuration. Try using it and see if that solves the issue and reopen if you still have the issue.
Wir haben heute Version 1.0.0 stable veröffentlicht. Diese Version bringt auch die Composer Cloud mit und ermöglicht die Abhängigkeitsauflösung auf unseren Servern. Sie kann bei den Hosting-Einstellungen aktiviert werden. Bitte damit erneut versuchen und Ticket wiedereröffnen, falls das Problem weiterhin besteht.
As an example, this one occurs on installation request.
Environment: