AWS EB问题无法在所有服务器上部署

时间:2017-05-29 09:07:17

标签: amazon-web-services elastic-beanstalk eb

昨天和今天我尝试在aws eb上部署,但我总是遇到这个错误:

INFO: Environment update is starting.
INFO: Deploying new version to instance(s).
INFO: Environment health has transitioned from Ok to Info. Command is executing on all instances.
WARN: Environment health has transitioned from Info to Severe. None of the instances are sending data.
ERROR: Failed to run npm install. Snapshot logs for more details.
ERROR: [Instance: i-0632a672238b6ee0b] Command failed on instance. Return code: 1 Output: (TRUNCATED).../opt/elasticbeanstalk/containerfiles/ebnode.py", line 166, in npm_install
    raise e
subprocess.CalledProcessError: Command '['/opt/elasticbeanstalk/node-install/node-v4.2.3-linux-x64/bin/npm', '--production', 'install']' returned non-zero exit status -9.
Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
ERROR: Unsuccessful command execution on instance id(s) 'i-0632a672238b6ee0b'. Aborting the operation.
ERROR: Failed to deploy application.

ERROR: Failed to deploy application.

昨天构建成功了,我试图推送旧版本,而另一个实例我只是尝试再次部署。现在每个实例都处于严重或降级的状态。

这是一个问题,我做错了吗?我做了我每天所做的所有步骤,直到现在我从未遇到过任何问题。即使在我上传旧的applicationzip后,没有任何改变。

1 个答案:

答案 0 :(得分:2)

我有完全相同的问题。在上周末,构建开始失败。由于日志,问题似乎是在运行 npm install 时,进程耗尽内存。无论是直接部署还是使用Docker容器都无关紧要。

我正在使用1 GB内存的免费层微实例。我只是无法理解为什么它以前工作,现在它不起作用,即使我部署了以前工作的相同版本...