Question

我知道这听起来很棒，但我无法弄清楚是什么问题。

我已经创建了一个带乘客的EB实例，按照教程，最后一步是运行

    INFO: Environment update is starting.
    INFO: Deploying new version to instance(s).
    ERROR: [Instance: i-71f70593] Command failed on instance. Return code: 137 Output: (TRUNCATED)... /var/app/ondeck/public/assets/priorizations/simplified/upper-5154a5b0c3e6cbf5463df08c05ab0bb4.png
    I, [2015-09-21T23:00:17.233813 #26607]  INFO -- : Writing /var/app/ondeck/public/assets/application-ea5935c63d274c4625db69541c62d788.js
    Killed (core dumped).
    Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/11_asset_compilation.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) '*****'. Aborting the operation.
    ERROR: Failed to deploy application.

哪个给了我

>>> ' '.join( [w for w in input.split() if len(w)>1] )
'23rwqw 34qf34 343fsdfd'

/var/log/eb-activity.log文件没什么有趣的（我认为）

有人可以帮助我吗？

Obs：该项目在本地和heroku都很好。

Answer 1

在资产预编译期间，我也遇到了同样的错误（Killed (core dumped)）。对我来说并不是间歇性的 - 我每次都会坚持得到它。

增加EC2实例大小为我解决了问题。我怀疑内存是缺乏资源 - 预编译期间100％的CPU对我来说从来都不是问题。

将Rails 4.1部署到AWS无法预编译资产

1 个答案: