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

问题描述 投票:3回答:1

昨天和今天,我尝试在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.

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

这是aws问题,我做错了吗?我做了所有日常工作,直到现在,我再也没有任何问题。即使我上传了旧的applicationzip,也没什么改变。

amazon-web-services amazon-elastic-beanstalk
1个回答
2
投票

我遇到完全相同的问题。在上一个周末,构建开始失败。由于日志的原因,问题似乎出在运行npm install时,进程内存不足。我直接部署还是使用Docker容器都没关系。

我正在使用具有1 GB内存的免费微型实例。我只是不明白为什么以前可以使用,现在即使我部署了以前使用过的相同版本也无法使用...

© www.soinside.com 2019 - 2024. All rights reserved.