AWS responses from [i-2a7fe91f] were received, but commands were not executed

I have a 64-bit Tomcat 7 server on AWS with default settings. I use Elastic Beanstalk to manage my instances. Sometimes, when I deploy a new version, it does not work and shows me an error:

Responses from [i-2a7fe91f] were received, but the commands failed.

The fact is that this happens half the time, not all times. When I get this error, I end the environment and create a new one with the same WAR file, and it works great! However, I was wondering if anyone knew what was really going on.

Here is the part of the log file that, in my opinion, is relevant:

 2013-05-23 17:12:02,555 [INFO] (20168 MainThread) [command.py-122] [root command execute] Executing command: Infra-WriteApplication2 - AWSEBAutoScalingGroup 2013-05-23 17:12:11,401 [INFO] (20168 MainThread) [command.py-130] [root command execute] Command returned: (code: 1, stdout: Error occurred during build: , stderr: None) 2013-05-23 17:12:11,432 [DEBUG] (20168 MainThread) [commandWrapper.py-60] [root commandWrapper main] Command result: {'status': 'FAILURE', 'results': [{'status': 'FAILURE', 'config_set': u'Infra-WriteApplication2', 'returncode': 1, 'events': [], 'msg': 'Error occurred during build: \n'}], 'api_version': '1.0'} 
+6
source share
2 answers

My problem was that the war file could not be loaded due to t1.micro RAM limitation. However, the error was not descriptive at all.

0
source

I came across the same error message. In my case, one of the commands in the .config file did not execute. There were no problems with the team itself, it turned out that I was missing a library that prevented the team from completing completely. The problem was resolved when I made the necessary changes to the requirements file.

What helped me in this case, I looked at the log file and found the culprit.

+3
source

Source: https://habr.com/ru/post/945705/


All Articles