Closed reluem closed 8 years ago
You should post code blocks either with indent or with triple backticks.
@fritzmg updated, sorry
Do you have shell access on that machine? The problem on your side is, that git takes more than 300 seconds to complete the command
git branch --no-color --no-abbrev -v
which should complete in around some milliseconds normally.
The MySQL problem is a follow up problem totally unrelated to this problem. Contao tries to save the session in the destructor which fails as the MySQL server has already closed the connection due to inactivity, it does so around 1 minute on average shared hosters.
no shell access on this system unfortunately.
a clone (database and Contao) of the running system on a different server (netcup), however, did work without problems.
Any way that I could (similarly to the #134 approach) use the netcup server, perform the git branch command and then copy back (and make it work on HE again)?
This will not work. You will get the correct vendor dir, however, all the symlinks will be missing. You have to fix your installation (and find out why git takes so long on your machine). Could you try to increase the composer log level in the Contao Settings and provide us with a complete transcript? Also, have you tried the detached mode?
okay.
I only see the normal error log. Is there a way to see a .log for composer on the server? The debug log setting did not have any effect on error.log.
Same with subprocess mode and standalone: HE' php path according to the FAQs
/usr/bin/php -d memory_limit=128M -d max_execution_time=60
no change at all..
No change at all????? When running stand alone, there MUST be something changed. And if it only is that you get a timeout and when going back to composer that you get a console window.
the linked page above seems suspicious to me:
Ein Pfad zu php wird in der Regel jedoch nur für CronJobs benötigt, da "normale" PHP Skripte von mod_php ausgeführt werden.
I doubt they are still running on mod_php
in 2016, if they really do: CHANGE HOSTING, DRAGONS AHEAD! :dragon:
Maybe you have some entry in system/logs/error.log
telling you that the process could not be spawned. To put long story short, I have no clue what hosting environment is available at HE as I have never used them.
just to be sure: I cannot access the composer inside Contao at all!
/contao/main.php?do=composer
throws the exception, I don't see the usual console window.
I did a phpinfo on HE: Server API Apache 2.0 Handler
Change hosting is the medium/long-term goal. ATM, however, functionality (as it was last week) would be preferred...
HE-Support did not really help (PHP version: PHP Version 5.6.18-1~he.0
):
Die einzige Änderung diese Woche ist die Deaktivierung von PHP5.3. Alle Domains die bis Dienstag PHP5.3 verwendet haben wurden von uns auf PHP5.6 umgestellt.
they offered, however, to follow a routine that triggers this error:
Bitte nennen Sie uns einen reproduzierbaren Weg - wir prüfen dann gerne ob es sich um einen Serverfehler oder einen Fehler in Ihren Skripten handelt.
Any ideas how they could reproduce the git-Error and maybe resolve the issue?
Reproducing this would involve debugging the problem onsite in your hosting package and detecting the settings needed to run composer and to inspect what versions of PHP you have running and what the config is. Sadly I lack the time to do this right now.
The php info you provided above indeed does imply having PHP running as mod_php which is pretty rare on shared hosting nowadays. Any chance you can change it to run as cgi?
My steps to troubleshoot would be:
proc_open
calls are executed correctly.did someone find a solution for problems with composer on HE WebHosting Basic?
proc_open and git are available according to the composer-check. Unfortunately, I don't have the relevant skills to do troubleshooting myself.
Up to this date, composer functionality is still not given.
@rabauss, did you encounter similar problems?
i think i have a solution the problem is that newest composer.phar is always searching for the version of composer.json via git. but git is not available as command in hosteurope-webpacks - so it ends with timeout!
you have to add the version-property manually into the contao-root/composer/composer.json https://getcomposer.org/doc/04-schema.md#version
{
"name": "local/website",
"description": "A local website project",
"version": "1.0.0",
"type": "project",
"license": "proprietary",
"require": {
......
also you should replace the composer.phar in contao-root/composer/ with the newest version (at the moment version 1.0.2) -- you need also #288
finally i recommend to change contao localconfig for composer.
set execution to detached for no php-limits - and disable auto-update
$GLOBALS['TL_CONFIG']['composerExecutionMode'] = 'detached';
$GLOBALS['TL_CONFIG']['composerVerbosity'] = 'VERBOSITY_NORMAL';
$GLOBALS['TL_CONFIG']['composerPhpPath'] = '/usr/bin/php -d memory_limit=1G -d max_execution_time=900 -d suhosin.executor.include.whitelist="http://,https://,phar" -d allow_url_fopen';
$GLOBALS['TL_CONFIG']['composerAutoUpdateLibrary'] = false;
yes, this was the solution!
Perfect, thank you so much!
edit: worked perfectly until I updated to the phar version you mentioned above!
$ /usr/bin/php -d memory_limit=1G -d suhosin.executor.include.whitelist="http://,https://,phar" -d allow_url_fopen composer.phar update --no-ansi --no-interaction -vvv --profile
Unable to create lock file: Permission denied
Failed to start up concurrent users module!
Running 5c9c9102400dc4e38b8ea91074f22c7014050159 (2016-04-24 14:55:55) with PHP 5.6.20-1~he.0 on Linux / 3.10.5-he-wp2005-x64+6+
Fatal error: Call to a member function writeError() on null in phar:///is/htdocs/wp1162560_5HWO9P0IN0/www/kinderweihnacht/composer/composer.phar/src/Composer/Console/Application.php on line 163
zend_mm_heap corrupted
going back to older version makes it work again!
any suggestions regarding this?
Please try the solutions suggested at http://stackoverflow.com/questions/2247977/what-does-zend-mm-heap-corrupted-mean
after getting into composer-extension without timeout, I also had some trouble with phar.
I have the same error
[15-Feb-2017 18:48:03 Europe/Berlin] PHP Fatal error: Uncaught exception 'Symfony\Component\Process\Exception\ProcessTimedOutException' with message 'The process "git branch --no-color --no-abbrev -v" exceeded the timeout of 300 seconds.' thrown in phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/vendor/symfony/process/Process.php on line 1198
#0 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/vendor/symfony/process/Process.php(361): Symfony\Component\Process\Process->checkTimeout()
#1 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/vendor/symfony/process/Process.php(203): Symfony\Component\Process\Process->wait()
#2 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/src/Composer/Util/ProcessExecutor.php(68): Symfony\Component\Process\Process->run(Array)
#3 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/src/Composer/Package/Version/VersionGuesser.php(94): Composer\Util\ProcessExecutor->execute('git branch --no...', NULL, '/is/htdocs/wp10...')
#4 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/src/Composer/Package/Version/VersionGuesser.php(67): Composer\Package\Version\VersionGuesser->guessGitVersion(Array, '/is/htdocs/wp10...')
#5 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/src/Composer/Package/Loader/RootPackageLoader.php(76): Composer\Package\Version\VersionGuesser->guessVersion(Array, '/is/htdocs/wp10...')
#6 phar:///is/htdocs/wp12345_WNDYR8W5HX/www/my_page/composer/composer.phar/src/Composer/Factory.php(348): Composer\Package\Loader\RootPackageLoader->load(Array, 'Composer\\Packag...', '/is/htdocs/wp10...')
#7 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/system/modules/!composer/src/Runtime.php(585): Composer\Factory->createComposer(Object(Composer\IO\BufferIO))
#8 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/system/modules/!composer/src/ClientBackend.php(300): ContaoCommunityAlliance\Contao\Composer\Runtime::createComposer(Object(Composer\IO\BufferIO))
#9 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/system/modules/!composer/src/ClientBackend.php(125): ContaoCommunityAlliance\Contao\Composer\ClientBackend->loadComposer()
#10 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/system/modules/core/classes/Backend.php(423): ContaoCommunityAlliance\Contao\Composer\ClientBackend->generate()
#11 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/system/modules/core/controllers/BackendMain.php(131): Contao\Backend->getBackendModule('composer')
#12 /is/htdocs/wp12345_WNDYR8W5HX/www/my_page/contao/main.php(20): Contao\BackendMain->run()
#13 {main}
on HostEurope WebPack L with Contao 3.5.24 ... I work allone at the backend and I updated all packages for few days (~09.2.17 ?)
If I click at icon "package manager" and wait five minutes response a error.
any older composer.phar don´t fix the problem
You did try adding the version
key as suggested by @rabauss in https://github.com/contao-community-alliance/composer-client/issues/285#issuecomment-214057249 ?
W O W ! ! !
... and it´s running with
"version": "1.0.0",
edit: is this the right repo, or composer-plugin?
Composer stopped working on HostEurope WebPack Basic since approx. yesterday.
Any composer install (repository install of composer client -> composer install on a new contao 3.5.x with an empty database), or click on "Paketverwaltung" on an existing installation (with composer being installed for several weeks now), lead to the following error:
any suggestions on this? As I said, clean install leads to the same problem.
/composer.json
/composer/composer.json: