Amazon Beanstalk Deployment Errors

Question

I run two environments and I get the same errors every time I deploy the application. These errors also occur when you deploy the Beanstalk sample application. Errors disappear when we create a new environment and deploy the same files in it .. for several days, at least, and then they return.

Instance: i-72715b7f Command failed on instance. An unexpected error has occurred ErrorCode: 0000000001. 

Environment update operation completed, but with errors. See the troubleshooting documentation for more information.

 Instance: i-85437188 Module: AWSEBAutoScalingGroup ConfigSet: null Command failed on instance. Return code: 1 Output: Error occurred during build: Command hooks failed . Script /opt/elasticbeanstalk/hooks/appdeploy/enact/99_reload_app_server.sh failed with returncode 1 Script /opt/elasticbeanstalk/hooks/appdeploy/pre/12_update_permissions.sh failed with returncode 1 

The app (the WordPress website) seems to work just fine even with these errors in events, except for occasional problems that act like traditional resolution errors (images cannot be uploaded or permalinks do not work). We used the same beanstalk application without any problems or errors. These errors also occur when you deploy the Beanstalk sample application.

This is the only fragment from the error log that seems to have any meaning.

 2014-09-17 19:47:08,825 ERROR Error encountered during build of Hook-EnactAppDeploy: Command hooks failed Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 511, in run_config CloudFormationCarpenter(config, self._auth_config).build(worklog) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 247, in build changes = CommandTool().apply(self._config.commands) File "/usr/lib/python2.6/site-packages/cfnbootstrap/command_tool.py", line 113, in apply raise ToolError(u"Command %s failed" % name) ToolError: Command hooks failed 2014-09-17 19:47:08,826 ERROR Unhandled exception during build: Command hooks failed Traceback (most recent call last): File "/opt/aws/bin/cfn-init", line 122, in <module> worklog.build(detail.metadata, configSets) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 117, in build Contractor(metadata).build(configSets, self) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 502, in build self.run_config(config, worklog) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 511, in run_config CloudFormationCarpenter(config, self._auth_config).build(worklog) File "/usr/lib/python2.6/site-packages/cfnbootstrap/construction.py", line 247, in build changes = CommandTool().apply(self._config.commands) File "/usr/lib/python2.6/site-packages/cfnbootstrap/command_tool.py", line 113, in apply raise ToolError(u"Command %s failed" % name) ToolError: Command hooks failed 

What is wrong here? How do we fix this?

Answer 1

The problem ended up being a damaged WordPress plugin. The plugin created a new folder in the /tmp every time the file was downloaded, but never deleted the folder. It will delete all files in the folder, but will never be a folder. Since customers used the site and continued to upload images, then these folders would be folded, and eventually it would fill in the /tmp . A fix for this plugin resolved the issue and it did not return.

Answer 2

It may be too late, but the entry is for posterity: whenever the root file system is populated with an EB instance, this error appears. There may be other reasons for this error, but that's for sure.

In our case, it was a chat logging option that shielded the development environment in the assembly and deployed by scoring /var/log . Fast eb health showed a warning about the form Degraded 100 % of root file system is in use. 0 MB free. Degraded 100 % of root file system is in use. 0 MB free. From there it was easy to clean.