ElasticBeanstalk, errore di distribuzione: ganci di comando (directoryHooksExecutor.py --path/opt/elasticbeanstalk/ganci/AppDeploy/pre /) non è riuscito

Question

questo errore:

ganci di comando (directoryHooksExecutor.py --path/opt/elasticbeanstalk/hooks/appdeploy/pre /) failed

dopo aver provato a distribuire tramite git aws.push.

Il dispiegamento non passare attraverso, l'evento che vengono gettati sono:

2014-05-20 15:41:46 UTC 0700 ERRORE [Instance: i-808b90df Modulo: AWSEBAutoScalingGroup ConfigSet: null] Comando non riuscito su istanza. Codice di ritorno: 1 Output: si è verificato un errore durante la compilazione: Ganci di comando non riusciti. 2014/05/20 15:41:43 UTC 0700 Script ERRORE /opt/elasticbeanstalk/hooks/appdeploy/pre/10_bundle_install.sh riuscita con returncode 1

Questo è il log degli errori:

2014- 05-20 22: 41: 43,767 [ERRORE] Ganci di comando (directoryHooksExecutor.py --path/opt/elasticbeanstalk/hooks/appdeploy/pre /) non riuscito 2014-05-20 22: 41: 43,768 [DEBUG] Output dei comandi di comando : 2014-05-20 22: 41: 43,768 [ERRORE] Errore durante la generazione di Hook-PreAppDeploy: Ganci di comando non riusciti Traceback (ultima chiamata ultima): File "/usr/lib/python2.6/site- packages/cfnbootstrap/construction.py ", riga 511, in run_config CloudFormationCarpenter (config, self._auth_config) .build (worklog) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", riga 247, nella build modifiche ['comandi'] = CommandTool(). Apply (self._config.commands) File "/usr/lib/python2.6/site-packages/cfnbootstrap/command_tool.py", riga 113, in applica raise ToolError (u "Comando% s fallito "% name) ToolError: Command hooks failed 2014-05-20 22: 41: 43,795 [ERROR] Eccezione non gestita durante la compilazione: Ganci di comando non riusciti Traceback (ultima chiamata ultima): File"/opt/aws/bin/cfn-init ", riga 122, in worklog.build (detail.metadata, configSets) File" /usr/lib/python2.6/site-packages/cfnbootstrap/construction.py ", lin e 117, in build Contraente (metadati) .build (configSets, self) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", riga 502, nella build self.run_config (config, worklog) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", riga 511, in run_config CloudFormationCarpenter (config, self._auth_config) .build (worklog) File "/ usr/lib/python2.6/site-packages/cfnbootstrap/construction.py ", riga 247, nella build modifiche ['commands'] = CommandTool(). apply (self._config.commands) File"/usr/lib/python2.6/site-packages/cfnbootstrap/command_tool.py ", riga 113, applicare raise ToolError (u" Command% s failed "% name) ToolError: Command hooks failed 2014-05-20 23: 35: 04,652 [DEBUG] Client CloudFormation inizializzato con endpoint https://cloudformation.us-west-1.amazonaws.com 2014-05-20 23: 35: 04,653 [DEBUG] Descrizione risorsa AWSEBAutoScalingGroup nello stack arn: aws: cloudformation: us-west-1 : 040951787496: stack/awseb-e-yz93miu6ma-stack/1bd7f720-da3f-11e3-a5f1-50fa003f9896

Qualsiasi idea?

Grazie

Answer 1

Ho riscontrato un problema simile su bundle_install.sh, usa $> eb logs e controlla il tuo /var/log/directory-hooks-executor.log, per me fallisce nell'installazione di gem 'forem'.

Answer 2

Ho un errore simile: /opt/elasticbeanstalk/hooks/appdeploy/pre/10_composer_install.sh failed with returncode 255 risulta essere il compositore il colpevole.

i registri trovati a /var/log/directory-hooks-executor.log:

2015-01-19 15:13:33,537 [INFO] (29969 MainThread) [directoryHooksExecutor.py-29] [root directoryHooksExecutor info] Executing script: /opt/elasticbeanstalk/hooks/appdeploy/ pre/10_composer_install.sh 
+ '[' -f composer.json ']' 
+ echo 'Found composer.json file. Attempting to install vendors.' 
Found composer.json file. Attempting to install vendors. 
+ composer.phar install --no-ansi --no-interaction --no-dev --prefer-dist 
Loading composer repositories with package information 
PHP Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///opt/elasticbeanstalk/support/composer.phar/ vendor/symfony/console/Symfony/Component/Console/Application.php:975 
#1 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(975): proc_open('stty -a | grep ...', Array, NULL, NULL,  NULL, Array) 
#2 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(853): Symfony\Component\Console\Application-> getSttyColumns() 
#3 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(818): Symfony\Component\Console\Application-> getTerminalDimensions() 
#4 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Applicat in phar:///opt/elasticbeanstalk/support/composer.phar/vendor/ symfony/console/Symfony/Component/Console/Application.php on line 975 
Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///opt/elasticbeanstalk/support/composer.phar/vendor/ symfony/console/Symfony/Component/Console/Application.php:975 
#1 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(975): proc_open('stty -a | grep ...', Array, NULL, NULL,  NULL, Array) 
#2 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(853): Symfony\Component\Console\Application-> getSttyColumns() 
#3 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php(818): Symfony\Component\Console\Application-> getTerminalDimensions() 
#4 phar:///opt/elasticbeanstalk/support/composer.phar/vendor/symfony/console/Symfony/Component/Console/Applicat in phar:///opt/elasticbeanstalk/support/composer.phar/vendor/ symfony/console/Symfony/Component/Console/Application.php on line 975 
2015-01-19 15:20:06,267 [ERROR] (29969 MainThread) [directoryHooksExecutor.py-33] [root directoryHooksExecutor error] Script /opt/elasticbeanstalk/hooks/appdeploy/ pre/10_composer_install.sh failed with returncode 255 

Secondo questa github issue i modi per risolvere questo problema è di aumentare la memory_limit nel php.ini.

Answer 3

Ho appena risolto un errore simile. Sembra che Elastic Beanstalk non sia stato in grado di far fronte a uno stato negativo in una delle istanze e semplicemente non sia stato possibile implementarlo, causando un'instabilità generale nell'ambiente EB.

Ho risolto riducendo il numero di istanze a 1 e ridistribuendo. Ciò ha mantenuto solo un buon esempio, ha ucciso il problematico e ha risolto il problema.