Are you deploying to a shared host such as Dreamhost?

I can't back it up with any proof, but if you are, my guess is that
during deployment, you are hitting CPU or memory usage limits and a
process watcher on the shared host is killing your compilation
process.

I've had some success in this case by manually uploading the
precompiled assets the first time only. From their on, the
assets:precompile task shouldn't be recompile assets that haven't
changed... so that might save you some CPU/memory, perhaps enough that
your deployment will resume normal functionality.
On Oct 22, 6:46 pm, Nicolas Buduroi wrote:
Hi, I've recently updated an application to 3.1.1 and Capistrano
started to fail at the assets:precompile task. It's a strange bug that
don't always happen (it actually worked a couple of time) and there's
no error message, it only display "Killed". Running the rake task
locally work though. I've reverted to 3.1.0 and now it work with
Capistrano.

Has something changed in 3.1.1 in regard to assets:precompile when
used from Capistrano?
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 2 | next ›
Discussion Overview
grouprubyonrails-talk @
categoriesrubyonrails
postedOct 22, '11 at 10:47p
activeOct 23, '11 at 6:16p
posts2
users2
websiterubyonrails.org
irc#RubyOnRails

2 users in discussion

Nicolas Buduroi: 1 post Jarrod: 1 post

People

Translate

site design / logo © 2021 Grokbase