我已经在ubuntu 12.04服务器上安装了nodejs，我想知道为什么我在编译资产时遇到问题，当我进入控制台时rails c我运行这个
ExecJS::Runtimes.best_available=> #<ExecJS::ExternalRuntime:0x0000000118cc88
@binary="nodejs",
@command=["nodejs", "node"],
@deprecated=false,
@encoding="UTF-8",
@name="Node.js (V8)",
@runner_path= "/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/execjs-1.4.0/lib/execjs/support/node_runner.js",
@ test_args =零， @ test_match =零＆GT;
当然我可以运行node或nodejs命令，这可能是错的，这是尝试编译资产后的错误
/home/bonsai/.rvm/rubies/ruby-1.9.3-p392/bin/ruby /home/bonsai/.rvm/gems/ruby-1.9.3-p392@global/bin/rake assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets
rake aborted!
Killed
(in /home/bonsai/bonsaierp/app/assets/javascripts/application.js.coffee)
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/execjs-1.4.0/lib/execjs/external_runtime.rb:142:in `exec_runtime'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/execjs-1.4.0/lib/execjs/external_runtime.rb:28:in `block in exec'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/execjs-1.4.0/lib/execjs/external_runtime.rb:41:in `compile_to_tempfile'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/execjs-1.4.0/lib/execjs/external_runtime.rb:27:in `exec'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/uglifier-1.3.0/lib/uglifier.rb:100:in `compile'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/compressors.rb:74:in `compress'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/processing.rb:265:in `block in js_compressor='
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/processor.rb:29:in `call'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/processor.rb:29:in `evaluate'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/tilt-1.3.6/lib/tilt/template.rb:77:in `render'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/context.rb:193:in `block in evaluate'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/context.rb:190:in `each'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/context.rb:190:in `evaluate'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/bundled_asset.rb:26:in `initialize'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:252:in `new'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:252:in `build_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/index.rb:93:in `block in build_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/caching.rb:19:in `cache_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/index.rb:92:in `build_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:169:in `find_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/index.rb:60:in `find_asset'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/static_compiler.rb:19:in `block in compile'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:219:in `block in each_logical_path'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:206:in `block (2 levels) in each_file'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:196:in `each'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:196:in `each_entry'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:204:in `block in each_file'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:203:in `each'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:203:in `each_file'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/sprockets-2.2.2/lib/sprockets/base.rb:217:in `each_logical_path'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/static_compiler.rb:18:in `compile'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:56:in `internal_precompile'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:70:in `block (3 levels) in <top (required)>'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:60:in `block (3 levels) in <top (required)>'
Tasks: TOP => assets:precompile:primary
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [/home/bonsai/.rvm/rubies/ruby-1.9.3-p392/b...]
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:12:in `ruby_rake_task'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:21:in `invoke_or_reboot_rake_task'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/gems/actionpack-3.2.13/lib/sprockets/assets.rake:29:in `block (2 levels) in <top (required)>'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/bin/ruby_noexec_wrapper:14:in `eval'
/home/bonsai/.rvm/gems/ruby-1.9.3-p392@rails3.2/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
答案 0 :(得分：6)
我也有同样的问题，当我使用Digital Ocean时也是如此。我假设你正在使用512MB的液滴。我给他们发了一张支持票，这是他们的答复：
＆＃34;通常，在512MB的Droplet上运行Nginx，Unicorn和Ruby on Rails，您将遇到内存问题。 我建议考虑升级到1GB的Droplet，并设置1GB的交换内存。＆＃34;
请注意，我仍然尝试在使用512MB droplet时设置1 GB交换内存，因为我没有在服务器上设置交换内存，但这实际上产生了相同的错误。 当我按照他/她的建议并升级到1GB液滴时，编译资产工作正常。
答案 1 :(得分：4)
您应该创建一个交换文件。这将从存储创建一些虚拟内存（数字海洋飞溅使用SSD，因此它应该相对较快）。
创建1GB交换文件，仅为root设置读/写权限，然后启用它[1]。
sudo dd if=/dev/zero of=/swapfile bs=1M count=1024
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
要使交换永久，请将以下行添加到/ etc / fstab的末尾
/swapfile none swap sw 0 0
我还强烈建议您按照Digital Ocean提供的本教程来优化您的Unicorn工作人员。 https://www.digitalocean.com/community/tutorials/how-to-optimize-unicorn-workers-in-a-ruby-on-rails-app
我目前正在使用Unicorn和Nginx运行两个Rails网站，并且没有任何此类问题。