rake资产预编译使用rails 3.2.11中止

时间:2013-02-18 09:51:39

标签: ruby-on-rails-3 rake asset-pipeline rails-3-upgrade

我必须运行rake资产:在机架空间服务器部署之前预编译命令,最近由于安全补丁和升级的JSON GEM而将最新的rails版本从3.2.9升级到3.2.11。

我收到以下错误并且rake abort。

 $> rake assets:precompile --trace
 ** Invoke assets:precompile:all (first_time)
 ** Execute assets:precompile:all
 ** Invoke assets:precompile:primary (first_time)
 ** Invoke assets:environment (first_time)
 ** Execute assets:environment
 ** Invoke environment (first_time)
 ** Execute environment
 ** Invoke tmp:cache:clear (first_time)
 ** Execute tmp:cache:clear
 ** Execute assets:precompile:primary

 rake aborted!
 Command failed with status (): [/usr/local/rvm/rubies/ruby-1.9.3-p385/bin/...]
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/lib/rake   /file_utils.rb:53:in `block in create_shell_runner'
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/lib/rake/file_utils.rb:45:in `call'
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/lib/rake/file_utils.rb:45:in `sh'
 /usr/local/rvm/gems/ruby-1.9.3-p385/gems/actionpack-3.2.11/lib/sprockets/assets.rake:12:in `ruby_rake_task'
 /usr/local/rvm/gems/ruby-1.9.3-p385/gems/actionpack-3.2.11/lib/sprockets/assets.rake:21:in `invoke_or_reboot_rake_task'
 /usr/local/rvm/gems/ruby-1.9.3-p385/gems/actionpack-3.2.11/lib/sprockets/assets.rake:29:in `block (2 levels) in <top (required)>'
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/lib/rake/application.rb:160:in  `standard_exception_handling'
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/lib/rake/application.rb:70:in `run'
 /usr/local/rvm/gems/ruby-1.9.3-p385@global/gems/rake-10.0.3/bin/rake:33:in `<top (required)>'
/usr/local/rvm/gems/ruby-1.9.3-p385@global/bin/rake:19:in `load'
/usr/local/rvm/gems/ruby-1.9.3-p385@global/bin/rake:19:in `<main>'
/usr/local/rvm/gems/ruby-1.9.3-p385/bin/ruby_noexec_wrapper:14:in `eval'
/usr/local/rvm/gems/ruby-1.9.3-p385/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => assets:precompile

对此有何解决方案?

1 个答案:

答案 0 :(得分:2)

可能是内存问题? 尝试升级VPS中的RAM