I have a 64 bit Tomcat 7 server on AWS with the default settings. I use Elastic Beanstalk to manage my instances. Sometimes when I deploy a new version, it doesn't work and shows me an error:
Responses from [i-2a7fe91f] were received, but the commands failed.
The thing is it happens half of the times, not all the times. When I get this error, I terminate the environment and create a new one with the same WAR file and it works fine! However, I was wondering if anyone knows what is really happening.
Here's a part of log file that I think 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'}
If the aws command cannot be found after first installing or updating the AWS CLI, you might need to restart your terminal for it to recognize any PATH updates. If the aws command cannot be found after first installing or updating the AWS CLI, it might not have been fully installed.
To validate a user's credentials with the AWS CLI, run the sts get-caller-identity command. The command returns details about the user's credentials if they are valid, otherwise it throws an error. Copied!
Use the describe-configuration-recorder-status command to check that the AWS Config has started recording the configurations of the supported AWS resources existing in your account. The recorded configurations are delivered to the specified delivery channel.
There are many reasons why a function might time out, but the most likely is that it was waiting on an IO operation to complete. Maybe it was waiting on another service (such as DynamoDB or Stripe) to respond. Within a Lambda invocation, the function might perform multiple IO operations.
I encountered the same error message. In my case one of the commands in the .config file did not execute. There was no problem with the command itself, it turned out that I was missing a library which prevented the command from executing fully. The problem was resolved when I made the necessary changes to the requirements file.
What helped in my case was looking through the log file and locating the culprit.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With